Re: amrecover missing files
interesting.. i havn't tried changing the gnutar used by my amanda.. now that I think about it.. I remember having to make changes on some old amanda setups.. I am about ready to try changing my compiler config.. I work on a very odd distribution (home grown) that has a slightly whack compiler setup.. and I'm going to try doing a build against our default libc5 compiler (don't ask.. it's not my fault, i'd be in debian bliss if I could) did you look at the index files manualy? what do they show.. that's thing that made me wonder.. the index files on disk are perfectly fine.. they show all the properly backed up data. but amindexd doesn't return all the listings. -ben On Fri, 7 Jun 2002, Jon LaBadie wrote: > On Fri, Jun 07, 2002 at 01:52:39PM -0500, Ben Kochie wrote: > > I am using indexing, and gnutar to backup all of my filesystems, I keep > > the indexes in /etc/amanda/backupset/index/ according to my amanda.conf > > file. > > > > backups are working properly, no errors reported. I can run amrestore on > > a tape and see all of the files that are supposed to be backed up.. I can > > also gunzip the files in the index, and see them listed.. > > > > but when I run amrecover, set the host/disk, and do an ls, i only see a > > few of the directories/files that are supposed to be backed up. it seems > > like something in amindexd is not working properly, and I have no idea > > what. > > > > has any other amanda users run into this problem? > > One of my systems has similar problems. But because this system is a > Windows 2000 system and I'm backing it up from an amanda client under > Cygwin, I thought it might have been the unusual setup I'm using. > > However I'm coming to believe others are having similar problems > so that it may not be my unique setup. > > A sample of my results. When I look at the D: partition, there are > 2100 > directories and files there. When I look at the amanda tape of a level 0 > of that partition, it seems all the files are there. And the size of the > dump is reasonable. > > But the index is certainly not. The index has 220 entries, 190 of them > directories. Very few, if any, of those are more than 3 levels down. > The 30 or so files are all in the top 2 directories. > > I originally did the cygwin client using gnutar 1.13.19. Now I'm using > 1.13.25 and seeing the same results. > > Suggestions? > > -- > Jon H. LaBadie [EMAIL PROTECTED] > JG Computing > 4455 Province Line Road(609) 252-0159 > Princeton, NJ 08540-4322 (609) 683-7220 (fax) >
tape balancing tied to incrementals enabled?
Hi, I have a number of directories which contain data files, and the sum total of them is big - several tapes worth. I have them split into a number of "disks" in the disklist file. When I want to back each up, I want the whole directory (disk) to be backed-up, without doing an incremental of just some files. It seemed easy to do - just set "skip-incr yes". But when I do this, Amanda seems to also skip the algorithm for spreading data evenly across tapes. So what I think will happen is that when they come due for level 0 again, I will get a big jump in the number of tapes needed for one particular day. I think the data spreading algorithm only works when incrementals are enabled. Is this correct? Thanks in advance! David _ Chat with friends online, try MSN Messenger: http://messenger.msn.com
Re: Amanda wants more tapes than I've got
On Wed, 5 Jun 2002, Jonathan Murray wrote: > Paul English wrote: > > > I'm getting the following error from amflush. I don't understand why it is > > requesting a new tape, I have runspercycle 10 and tapecycle 11. This is my > > first time through the cycle, and I've created an labelled Daily-00 > > through Daily-10 (and Daily-10 is the one which overflowed). > > This is amanda version 2.4.2p2 > > > > *** A TAPE ERROR OCCURRED: [cannot overwrite active tape Daily-00]. > > Some dumps may have been left in the holding disk. > > Run amflush again to flush them to tape. > > The next tape Amanda expects to use is: a new tape. > > > > Thanks, > > Paul > > > runspercycle 10 ? > Does that mean 10 weeks? That might explain why it won't let you > overwrite them. No, that's just how many times it runs during a 2 week cycle ( 5 times / week - once each weekday). I figured it out - somehow my tape labelling had gotten confused. A brand new unused tape was labelled Daily-07, and no tape was actually labelled and used by amanda as Daily-08. Paul
Re: amrecover missing files
On Fri, Jun 07, 2002 at 01:52:39PM -0500, Ben Kochie wrote: > I am using indexing, and gnutar to backup all of my filesystems, I keep > the indexes in /etc/amanda/backupset/index/ according to my amanda.conf > file. > > backups are working properly, no errors reported. I can run amrestore on > a tape and see all of the files that are supposed to be backed up.. I can > also gunzip the files in the index, and see them listed.. > > but when I run amrecover, set the host/disk, and do an ls, i only see a > few of the directories/files that are supposed to be backed up. it seems > like something in amindexd is not working properly, and I have no idea > what. > > has any other amanda users run into this problem? One of my systems has similar problems. But because this system is a Windows 2000 system and I'm backing it up from an amanda client under Cygwin, I thought it might have been the unusual setup I'm using. However I'm coming to believe others are having similar problems so that it may not be my unique setup. A sample of my results. When I look at the D: partition, there are > 2100 directories and files there. When I look at the amanda tape of a level 0 of that partition, it seems all the files are there. And the size of the dump is reasonable. But the index is certainly not. The index has 220 entries, 190 of them directories. Very few, if any, of those are more than 3 levels down. The 30 or so files are all in the top 2 directories. I originally did the cygwin client using gnutar 1.13.19. Now I'm using 1.13.25 and seeing the same results. Suggestions? -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Amdump and Timeouts
Hello amanda-users, I have successfully backed up a large file system on a remote machine at level 0. Now when I am ready to backup again, this time at level 1, it is timing out. I suspect a possible firewall problem but not sure at this point, from my amdump log file I see the following: dumper: pid 1390 executable dumper version 2.4.2p2, using port 821 dumper: dgram_bind: socket bound to 0.0.0.0.820 dumper: pid 1389 executable dumper version 2.4.2p2, using port 820 dumper: dgram_bind: socket bound to 0.0.0.0.819 dumper: pid 1388 executable dumper version 2.4.2p2, using port 819 dumper: dgram_bind: socket bound to 0.0.0.0.818 dumper: pid 1387 executable dumper version 2.4.2p2, using port 818 On the client in amandad log file I see: amandad: dgram_recv: timeout after 10 seconds amandad: waiting for ack: timeout, retrying amandad: dgram_recv: timeout after 10 seconds amandad: waiting for ack: timeout, retrying amandad: dgram_recv: timeout after 10 seconds amandad: waiting for ack: timeout, retrying amandad: dgram_recv: timeout after 10 seconds amandad: waiting for ack: timeout, retrying amandad: dgram_recv: timeout after 10 seconds amandad: waiting for ack: timeout, giving up! amandad: pid 12794 finish time Fri Jun 7 13:41:53 2002 Would these be the ports involved in the currently running amdump? I may have overlooked this in the docs and FAQ, but I thought that the three ports 10080, 10082, 10082, are the ports involved? Amcheck has no problem. Ideas? Thanks in advance,
Re: reusing tape on sun storedge L280 library
Hi, We have a Sun StorEdge L280 but attached to a x86 machine running Linux. There may be some differences in configuration for you, but we have no problem advancing round-robin through the tapes. On Fri, 2002-06-07 at 16:23, Richard Chen wrote: > Hi, > I am evaluating using amanda to control a > sun storedge L280 library tape drive system (Quantum DLT7000) > connected to a sparc solaris server. I want to know if amanda > is able to cycle through and reuse the tapes in the 6 slots > on the drive. 6 slots? Ours is 8, carrying 7 tapes and 1 cleaning cartridge. No problems having amanda by-pass the cleaning cartridge, either. > > The problem is that using solaris mt command: > > # mt -f /dev/rmt/0 offline > > I can only cycle through the tapes in the 6 slots once. > Once the last slot has been used, the drive goes into 'loader ready' > state and the tapes in any of the slots are not loaded anymore. > One has to physically load the tape using the front control panel > on the tape drive. This is not acceptable because the server > is located at a remote data center and we want to reuse the tape > many times before changing them. > > Does anyone have any exprience using amanda to control this > kind of tape drive automatically? > > Thanks for any info. > > Richard >
reusing tape on sun storedge L280 library
Hi, I am evaluating using amanda to control a sun storedge L280 library tape drive system (Quantum DLT7000) connected to a sparc solaris server. I want to know if amanda is able to cycle through and reuse the tapes in the 6 slots on the drive. The problem is that using solaris mt command: # mt -f /dev/rmt/0 offline I can only cycle through the tapes in the 6 slots once. Once the last slot has been used, the drive goes into 'loader ready' state and the tapes in any of the slots are not loaded anymore. One has to physically load the tape using the front control panel on the tape drive. This is not acceptable because the server is located at a remote data center and we want to reuse the tape many times before changing them. Does anyone have any exprience using amanda to control this kind of tape drive automatically? Thanks for any info. Richard
Re: cruft file ?
On Fri, 7 Jun 2002, Marcelo Souza wrote: - Hi all, - - What those "ignoring cruft file" mean? The directory you have designated as "holdingdisk" probaly has some files amanda does not recognize in it. - TIA, - - - Marcelo - - (...) - STATISTICS: - Total Full Daily - - Dump Time (hrs:min)2:23 2:22 0:00 (0:00 start, 0:01 idle) - Output Size (meg) 10919.810919.80.0 - Original Size (meg) 10919.810919.80.0 - Avg Compressed Size (%) -- -- -- - Tape Used (%) 60.7 60.70.0 - Filesystems Dumped1 1 0 - Avg Dump Rate (k/s) -- -- -- - Avg Tp Write Rate (k/s) 1315.5 1315.5-- - - - NOTES: - amflush: host1.sd2a.0.1: ignoring cruft file. - amflush: host1.sd2a.0.2: ignoring cruft file. - amflush: host1.sd2a.0.3: ignoring cruft file. - amflush: host1.sd2a.0.4: ignoring cruft file. - amflush: host1.sd2a.0.5: ignoring cruft file. - taper: tape host1_MAIL3 kb 11181824 fm 1 [OK] - - - DUMP SUMMARY: - DUMPER STATS TAPER STATS - HOSTNAME DISK L ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s - -- -- -- - host1 sd2a 0 11181824 11181824 -- N/AN/A 141:40 1315.5 - - (brought to you by Amanda version 2.4.1p1) - - -- -- Stephen Carville UNIX and Network Administrator DPSI (formerly Ace USA Flood Services) 310-342-3602 [EMAIL PROTECTED]
cruft file ?
Hi all,
What those "ignoring cruft file" mean?
TIA,
- Marcelo
(...)
STATISTICS:
Total Full Daily
Dump Time (hrs:min)2:23 2:22 0:00 (0:00 start, 0:01 idle)
Output Size (meg) 10919.810919.80.0
Original Size (meg) 10919.810919.80.0
Avg Compressed Size (%) -- -- --
Tape Used (%) 60.7 60.70.0
Filesystems Dumped1 1 0
Avg Dump Rate (k/s) -- -- --
Avg Tp Write Rate (k/s) 1315.5 1315.5--
NOTES:
amflush: host1.sd2a.0.1: ignoring cruft file.
amflush: host1.sd2a.0.2: ignoring cruft file.
amflush: host1.sd2a.0.3: ignoring cruft file.
amflush: host1.sd2a.0.4: ignoring cruft file.
amflush: host1.sd2a.0.5: ignoring cruft file.
taper: tape host1_MAIL3 kb 11181824 fm 1 [OK]
DUMP SUMMARY:
DUMPER STATS TAPER STATS
HOSTNAME DISK L ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
-- -- --
host1 sd2a 0 11181824 11181824 -- N/AN/A 141:40 1315.5
(brought to you by Amanda version 2.4.1p1)
amrecover missing files
I am using indexing, and gnutar to backup all of my filesystems, I keep the indexes in /etc/amanda/backupset/index/ according to my amanda.conf file. backups are working properly, no errors reported. I can run amrestore on a tape and see all of the files that are supposed to be backed up.. I can also gunzip the files in the index, and see them listed.. but when I run amrecover, set the host/disk, and do an ls, i only see a few of the directories/files that are supposed to be backed up. it seems like something in amindexd is not working properly, and I have no idea what. has any other amanda users run into this problem? here is my amindexd log for one of my amrecover sessions. amindexd: debug 1 pid 5 ruid 3930 euid 3930 start time Fri Jun 7 13:35:51 2002 amindexd: version 2.4.3b3 < 220 staff AMANDA index server (2.4.3b3) ready. > SECURITY USER root bsd security: remote host staff.math.umn.edu user root local user amanda amandahosts security check passed < 200 Access OK > DATE 2002-06-07 < 200 Working date set to 2002-06-07. > SCNF staff < 200 Config set to staff. > HOST staff < 200 Dump host set to staff. > DISK / < 501 No index records for disk: /. Invalid? > DISK root < 501 No index records for disk: root. Invalid? > HOST staff < 200 Dump host set to staff. > DISK sdb5 - 2002-06-06 0 STAFF3 4 < 200 Disk set to sdb5. > OISD / Uncompress command: /bin/gzip -dc '/etc/amanda/staff/index/staff/sdb5/20020606_0.gz' 2>/dev/null | sort > '/etc/amanda/staff/index/staff/sdb5/20020606_0' f /etc/amanda/staff/index/staff/sdb5/20020606_0 < 200 "/" is a valid directory > OLSD / < 200- Opaque list of / < 201- 2002-06-06 0 STAFF3 /download/ < 201- 2002-06-06 0 STAFF3 /home/ < 201- 2002-06-06 0 STAFF3 /newprofiles/ < 201- 2002-06-06 0 STAFF3 /profiles/ < 201- 2002-06-06 0 STAFF3 /staffdata/ < 200 Opaque list of / > QUIT Removing index file: /etc/amanda/staff/index/staff/sdb5/20020606_0 < 200 Good bye. amindexd: pid 5 finish time Fri Jun 7 13:39:17 2002 I look at the directory on the local filesystem, and there should be a total of 12 directoryies and 9 files. also the same problem happens for subdirectories.
Re: amanda This account is currently not available.
On Fri, 7 Jun 2002, tom wrote: >first off I'm real real green at this Unix stuff. Person that used to take >care of this where I work left and now someone forgot to change the tape and >I need to perform an amflush. > >When I go to do this I get this error message " amflush: must run amflush as >user amanda " > >I try and login as amanda and I get this error message " This account is >currently not available." > >How do I make the amanda account available so I can do the flush? You can likely work the appropriate mojo by running (as root): su - amanda -c "/usr/local/sbin/amflush Config" Of course adjust /usr/local/sbin to point to your amanda installation if it differs and Config should be Daily, Monthly, or what have you. -- Brandon D. Valentine <[EMAIL PROTECTED]> Computer Geek, Center for Structural Biology "This isn't rocket science -- but it _is_ computer science." - Terry Lambert on [EMAIL PROTECTED]
Re: amanda This account is currently not available.
On Fri, 7 Jun 2002, tom wrote: - first off I'm real real green at this Unix stuff. Person that used to take - care of this where I work left and now someone forgot to change the tape and - I need to perform an amflush. - - When I go to do this I get this error message " amflush: must run amflush as - user amanda " - - I try and login as amanda and I get this error message " This account is - currently not available." - - How do I make the amanda account available so I can do the flush? What platform? As root, try 'su - amanda'. I never allow logins as amanda and setup the system so backup operators can su to the amanda user via sudo. If the above does not work then you may need to create the user. Check the amadna directory to get the correct uid and gid. -- -- Stephen Carville UNIX and Network Administrator DPSI (formerly Ace USA Flood Services) 310-342-3602 [EMAIL PROTECTED]
Re: amrestore problems
I guess it really was a permission problem. I added read permission to all on the tape device and I can extract files now. Anyone know why this is necessary? Permissions on the devices were: crw-rw1 root disk 9, 128 Aug 30 2001 /dev/nst0 and amanda ia member of the 'disk' group $ id amanda uid=250(amanda) gid=4(adm) groups=4(adm),6(disk) This seems to be OK for writing but not for reading. Is this an amanda feature? On Thu, 6 Jun 2002, Stephen Carville wrote: - I recently moved from solaris to linux so I am testing amrestore - again. I keep getting the following error: - - EOF, check amidxtaped.debug file on chena. - amrecover: short block 0 bytes - UNKNOWN file - amrecover: Can't read file header - extract_list - child returned non-zero status: 1 -- -- Stephen Carville UNIX and Network Administrator DPSI (formerly Ace USA Flood Services) 310-342-3602 [EMAIL PROTECTED]
Re: amanda This account is currently not available.
tom writes: > > I try and login as amanda and I get this error message " This account is > currently not available." > > How do I make the amanda account available so I can do the flush? Sounds like you're using FreeBSD, or another Unix that defaults the shell to a "nologin" script. You just need to change amanda's shell (the last field in /etc/passwd) to something valid, like /bin/sh or similar. The command is, depending on your OS: chsh usermod vipw # if the above two don't work vi /etc/passwd # last resort Dan -- [EMAIL PROTECTED] www.nodewarrior.org ignorami: n: The art of folding problem users into representational shapes.
amanda This account is currently not available.
first off I'm real real green at this Unix stuff. Person that used to take care of this where I work left and now someone forgot to change the tape and I need to perform an amflush. When I go to do this I get this error message " amflush: must run amflush as user amanda " I try and login as amanda and I get this error message " This account is currently not available." How do I make the amanda account available so I can do the flush? Tom Spencer, Technical Support Specialist [EMAIL PROTECTED] © 1995-1999 Northumbria EAGLE PO Box 220 26 Chapel Street Cobourg, ON Canada K9A 4K5 ph: (905) 373-9313 fax:(905) 373-1801
Re: Problems with amlabel: Value too large for defined data type (SOLVED)
I checked on the previous postings and looks like a
Linux Kernel thing; When i installed amanda i was
using 2.4.7 and then i upgraded to 2.4.18;
Recompiling didn't help either so i decided to upgrade
to the latest beta version (amanda-2.4.3b3) and looks
like that solved the amlabel problem:
[amanda@linux0107 amanda-2.4.3b3]$ amlabel
NEWBREAK_TAPE NEWBREAK_TAPE01
rewinding, reading label NEWBREAK_TAPE01
rewinding, writing label NEWBREAK_TAPE01, checking
label, done.
[amanda@linux0107 amanda-2.4.3b3]$ eject /dev/st0
Hope this info helps others with the same problem.
--- José Vicente Núñez Zuleta <[EMAIL PROTECTED]>
wrote:
> Greetings,
>
> I'm running amanda on a Redhat 7.2 server using the
> hard disk as backup repository; Recently we bougth a
> Benchmark DLT1 tape unit and Linux was able to
> detect
> it with no problems (also i created a sepparate
> configuration for the new tape unit). I run the
> tapetype program and got the following setup for the
> tape unit:
>
> define tapetype DLT1 {
> comment "BENCHMARK DLT1 tape unit"
> length 34618 mbytes
> filemark 21 kbytes
> speed 1395 kbytes
> }
>
> (i added this definition to my amanda.conf file; But
> when i try to label the tape i got the following
> error:
>
> [amanda@linux0107 amanda]$ amlabel NEWBREAK_TAPE
> NEWBREAK_TAPE01
> rewinding, reading label, reading label: Value too
> large for defined data type
> rewinding, writing label NEWBREAK_TAPE01, checking
> label
> amlabel: reading label: Value too large for defined
> data type
>
> Here is my amanda build version:
>
> [amanda@linux0107 amanda]$ amadmin NEWBREAK_TAPE
> version
> build: VERSION="Amanda-2.4.3b1"
>BUILT_DATE="Sun Dec 9 10:05:03 EST 2001"
>BUILT_MACH="Linux linux0107 2.4.7-10smp #1
> SMP
> Thu Sep 6 17:09:31 EDT 2001 i686 unknown"
>CC="gcc"
> paths: bindir="/home/amanda/bin"
> sbindir="/home/amanda/sbin"
>libexecdir="/home/amanda/libexec"
>mandir="/home/amanda/man"
> AMANDA_TMPDIR="/tmp/amanda"
>AMANDA_DBGDIR="/tmp/amanda"
>CONFIG_DIR="/home/amanda/etc/amanda"
> DEV_PREFIX="/dev/"
>RDEV_PREFIX="/dev/" DUMP="/sbin/dump"
>RESTORE="/sbin/restore"
> SAMBA_CLIENT="/usr/bin/smbclient"
>GNUTAR="/bin/tar"
> COMPRESS_PATH="/usr/bin/gzip"
>UNCOMPRESS_PATH="/usr/bin/gzip"
> MAILER="/usr/bin/Mail"
>
>
listed_incr_dir="/home/amanda/var/amanda/gnutar-lists"
> defs: DEFAULT_SERVER="linux0107"
> DEFAULT_CONFIG="NEWBREAK"
>DEFAULT_TAPE_SERVER="linux0107"
>DEFAULT_TAPE_DEVICE="/dev/null" HAVE_MMAP
> HAVE_SYSVSHM
>LOCKING=POSIX_FCNTL SETPGRP_VOID DEBUG_CODE
>AMANDA_DEBUG_DAYS=4 BSD_SECURITY
> USE_AMANDAHOSTS
>CLIENT_LOGIN="amanda" FORCE_USERID HAVE_GZIP
>COMPRESS_SUFFIX=".gz"
> COMPRESS_FAST_OPT="--fast"
>COMPRESS_BEST_OPT="--best"
> UNCOMPRESS_OPT="-dc"
>
> [amanda@linux0107 amanda]$ cat /proc/scsi/scsi
> Attached devices:
> Host: scsi0 Channel: 00 Id: 02 Lun: 00
> Vendor: QUANTUM Model: DLT7000 Rev: 391B
> Type: Sequential-AccessANSI SCSI
> revision: 02
>
> I'm using the /dev/nst0 device (no rewind) on my
> amanda.conf configuration.
>
>
> Any ideas?
>
> Thanks in advance.
>
> PD: the amanda server is working just fine with the
> disk configuration.
>
> =
> José Vicente Nuñez Zuleta ([EMAIL PROTECTED])
> Newbreak System Administrator
> (http://www.newbreak.com)
> Office Phone: 203-355-1511, 203-355-1510
> Fax:203-355-1512
> Cellular Phone: 203-570-7078
>
> __
> Do You Yahoo!?
> Yahoo! - Official partner of 2002 FIFA World Cup
> http://fifaworldcup.yahoo.com
=
José Vicente Nuñez Zuleta ([EMAIL PROTECTED])
Newbreak System Administrator (http://www.newbreak.com)
Office Phone: 203-355-1511, 203-355-1510
Fax:203-355-1512
Cellular Phone: 203-570-7078
__
Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup
http://fifaworldcup.yahoo.com
Dump during estimation
Hi, Is there a way to make amanda start a backup immediately after estimating a patition? Rather than waiting until all estimations are done. My intermittent problems with backups timing out occuring only during dumps (amcheck finds nothing) is still happening. However, I jacked up the dtimeout in amanda.conf and that clipped the number of clients that time out to a lower average (of 2 from 5). There does seem to be a limit to the positive effects, though. I increased the etimeout to a ridiculous number (99), and had a higher ratio of timeouts occur. I am currently testing out the maxdumps value to see if that has any effect. For those of you with intermittent timeouts, try increasing the timeout values (dtimeout, ctimeout, etimeout). My guess is that etimeout would have less of an effect than dtimeout, if estimations are going fine. But that's just a guess. I notice that the partitions most likely to timeout are those that finish estimation first. I was wondering if there's a way to get amanda to start dumping a partition as soon as estimating that partition is finished. I'd like to test it so the dumps don't need to wait for the slowest estimation. There doesn't seem to be anything I could find in the FAQ or lists. Thanks in advance, Lalo
Problems with amlabel: Value too large for defined data type
Greetings,
I'm running amanda on a Redhat 7.2 server using the
hard disk as backup repository; Recently we bougth a
Benchmark DLT1 tape unit and Linux was able to detect
it with no problems (also i created a sepparate
configuration for the new tape unit). I run the
tapetype program and got the following setup for the
tape unit:
define tapetype DLT1 {
comment "BENCHMARK DLT1 tape unit"
length 34618 mbytes
filemark 21 kbytes
speed 1395 kbytes
}
(i added this definition to my amanda.conf file; But
when i try to label the tape i got the following
error:
[amanda@linux0107 amanda]$ amlabel NEWBREAK_TAPE
NEWBREAK_TAPE01
rewinding, reading label, reading label: Value too
large for defined data type
rewinding, writing label NEWBREAK_TAPE01, checking
label
amlabel: reading label: Value too large for defined
data type
Here is my amanda build version:
[amanda@linux0107 amanda]$ amadmin NEWBREAK_TAPE
version
build: VERSION="Amanda-2.4.3b1"
BUILT_DATE="Sun Dec 9 10:05:03 EST 2001"
BUILT_MACH="Linux linux0107 2.4.7-10smp #1 SMP
Thu Sep 6 17:09:31 EDT 2001 i686 unknown"
CC="gcc"
paths: bindir="/home/amanda/bin"
sbindir="/home/amanda/sbin"
libexecdir="/home/amanda/libexec"
mandir="/home/amanda/man"
AMANDA_TMPDIR="/tmp/amanda"
AMANDA_DBGDIR="/tmp/amanda"
CONFIG_DIR="/home/amanda/etc/amanda"
DEV_PREFIX="/dev/"
RDEV_PREFIX="/dev/" DUMP="/sbin/dump"
RESTORE="/sbin/restore"
SAMBA_CLIENT="/usr/bin/smbclient"
GNUTAR="/bin/tar" COMPRESS_PATH="/usr/bin/gzip"
UNCOMPRESS_PATH="/usr/bin/gzip"
MAILER="/usr/bin/Mail"
listed_incr_dir="/home/amanda/var/amanda/gnutar-lists"
defs: DEFAULT_SERVER="linux0107"
DEFAULT_CONFIG="NEWBREAK"
DEFAULT_TAPE_SERVER="linux0107"
DEFAULT_TAPE_DEVICE="/dev/null" HAVE_MMAP
HAVE_SYSVSHM
LOCKING=POSIX_FCNTL SETPGRP_VOID DEBUG_CODE
AMANDA_DEBUG_DAYS=4 BSD_SECURITY
USE_AMANDAHOSTS
CLIENT_LOGIN="amanda" FORCE_USERID HAVE_GZIP
COMPRESS_SUFFIX=".gz"
COMPRESS_FAST_OPT="--fast"
COMPRESS_BEST_OPT="--best" UNCOMPRESS_OPT="-dc"
[amanda@linux0107 amanda]$ cat /proc/scsi/scsi
Attached devices:
Host: scsi0 Channel: 00 Id: 02 Lun: 00
Vendor: QUANTUM Model: DLT7000 Rev: 391B
Type: Sequential-AccessANSI SCSI
revision: 02
I'm using the /dev/nst0 device (no rewind) on my
amanda.conf configuration.
Any ideas?
Thanks in advance.
PD: the amanda server is working just fine with the
disk configuration.
=
José Vicente Nuñez Zuleta ([EMAIL PROTECTED])
Newbreak System Administrator (http://www.newbreak.com)
Office Phone: 203-355-1511, 203-355-1510
Fax:203-355-1512
Cellular Phone: 203-570-7078
__
Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup
http://fifaworldcup.yahoo.com
Re: configuration problem
Have you run the program amlabel ? It will create the amada labels at the head of the tape so that amanda will accept them. Jerry Stretch Industry Inet - Original Message - From: "Dovli" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, June 07, 2002 8:10 AM Subject: configuration problem > Hello > > I have installed amanda on a Linux server that has a Seagate STT8000A > tape device but I could not manage to get amanda to use my tape device. > Here's the output of amcheck: > Amanda Tape Server Host Check > - > Holding disk /dumps/amanda: 20584876 KB disk space available, that's plenty > ERROR: /dev/ht0: not an amanda tape >(expecting a new tape) > > The tape device is functional otherwise, > What did I do wrong? > Thank you very much for your support. > Dovli >
Success!!!!
First goal has been achieved - the file system has backed up successfully when it is exclusively in the disklist. Also, many thanks for the recommendation of Mammoth Tool. I downloaded it from the Exabyte Website and it actually confirmed that the EZ17 was NOT hardware compressing (unlike the helpful guy I phoned at Exabyte who told me that HW compression was on permanently for the EZ17. Regards Kenny -- Kenny MacPherson IT Manager DDI: +44 131 272 7091 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Gene Heskett Sent: 06 June 2002 02:43 To: Kenny MacPherson; [EMAIL PROTECTED] Subject: Re: Can AMANDA only backup < 24GB partitions??? On Wednesday 05 June 2002 05:28 pm, Kenny MacPherson wrote: >Stephen, Jon, Lalo and Gene (and anyone else!) > >Thanks for the response. It's very helpful - I wasn't picking on > you Lalo but when I saw the 24GB quoted, alarm bells started > ringing, so it's good to here that my 55GB should be backup-able. > >As far as the holding disk goes, I only have 35GB disk, and I'm on > 32bit Sol 7. AMANDA is configured to use "chunks" of just under > 2GB each. > >The errors tend to be: > >FAILURE AND STRANGE DUMP SUMMARY: > toronto/home3 lev 0 FAILED [out of tape] You're walking on ground I haven't, at least on that sort of a scale. My system here is a CTL-96 Seagate drive but only a 4 slot magazine, so I have 3x about 3.7 gb tapes available. Wary of running an individual partition line in the disklist over the capacity of the tape, I've actually specified my /usr by each individual subdir which even keeps the downloads catchall under 3.7 gb. In this manner, I never ask amanda to span to the next tape, and I have sufficient tapes and days in the cycle that it can do 2 to 4 level 0's in each nightly run, getting it all at level 0 in just 3 or 4 days out of the 7 I allow. Amanda cannot span to the next tape with the leftover portion of a file, but will instead backup to the head (of I think that particular 2gb hunk, but it might be to that whole specified line in the disklist), load the next tape and try it again. In that event, a partition spec in the disklist thats larger than the holding area sounds like a recipe for trouble, and you should probably break the disklist up into smaller pieces by specifying it as subdirs, one per line. > taper: FATAL syncpipe_get: w: unexpected EOF > >or > >FAILURE AND STRANGE DUMP SUMMARY: > toronto/home3 lev 0 FAILED [data timeout] > toronto/home5 lev 0 FAILED [out of tape] > taper: FATAL syncpipe_get: w: unexpected EOF > toronto/home5 lev 0 FAILED ["data write: Broken pipe"] > toronto/home5 lev 0 FAILED [dump to tape failed] > >While this points the finger at the EZ17 library, The Mammoth 2 > drive inside it (AFAICT) should take upto 150GB on it 225m AME > tapes I use - the EZ17 is itself reckoned to do up to a 1TB but > that's probably by spanning 7 tapes together! > >The other possibility I consider is: may the point of failure be > when the holding disk hits 35GB, do the 2GB chunks waiting to get > "held" clash with the 2GB chunks coming off onto the tape? Thats a possibility I think. But since amanda does a decent job of multithreading, sometimes a re-arrangement of the order of the disklist can fix it so taper has enough writes to tape to stay ahead of it for a while. For this, amstatus /config/ while amdump is runnnig, can when it works can be quite educational. My copy seems to have some syntax gotcha's in it ATM, latest 2.4.3b3 snapshot. (Yeah, I have a little spare blood :-) >One thing I would love to do is turn the hardware compression off. > However, while the "standalone" Mammoth 2 drive has this option > in its LCD driven menu, there is no option in the LCD menu of the > EZ17! Is there somewhere I can do this at software level on my > Solaris 7 Ultra 2 (st.conf?) Thats a Solaris system? I'd first verify that you are using a device thats non-compression since I'm told Solaris controls the hardware compression via the device selection. However, if there are options in the menu's, or even hidden dip-switches, I'd certainly try to force the issue to get it turned off and then let amanda do it because it can do it better if you have the cpu horsepower. One thing I've run into with my puny little DDS-2 tapes is that once the tape has been written to with the compression on, its abominably difficult to get its auto-detected compression turned back off. Part of the problem in running hardware compression is that different filetypes will compress less, or more, than average, with the end result being that amanda gets badly blind-sided regarding it view of how much a tape can hold. With hardware compression off, and amanda doing oh, lets say gzip at its highest compression ratio, then amanda can keep track of every byte that goes to the tape *after* compression, thereby giving it a good indication of how much it can
Re: configuration problem
On Fri, 7 Jun 2002 at 4:10pm, Dovli wrote > I have installed amanda on a Linux server that has a Seagate STT8000A > tape device but I could not manage to get amanda to use my tape device. > Here's the output of amcheck: > Amanda Tape Server Host Check > - > Holding disk /dumps/amanda: 20584876 KB disk space available, that's plenty > ERROR: /dev/ht0: not an amanda tape >(expecting a new tape) > > The tape device is functional otherwise, > What did I do wrong? > Thank you very much for your support. 1) You need to use the non-rewinding tape device -- /dev/nht0 2) You need to label your tapes before amanda can use them -- 'man amlabel' -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
configuration problem
Hello I have installed amanda on a Linux server that has a Seagate STT8000A tape device but I could not manage to get amanda to use my tape device. Here's the output of amcheck: Amanda Tape Server Host Check - Holding disk /dumps/amanda: 20584876 KB disk space available, that's plenty ERROR: /dev/ht0: not an amanda tape (expecting a new tape) The tape device is functional otherwise, What did I do wrong? Thank you very much for your support. Dovli Here is my configuration file: ## !!! WARNING !!! !!! WARNING !!! !!! WARNING !!! !!! WARNING !!! ### ### ### ### This file is not meant to be installed "as is", and in fact, it ### ### WILL NOT WORK! You must go through it and make changes appropriate ### ### to your own situation. See the documentation in this file, in the ### ### "man amanda" man page, in the "docs" directory and at the Amanda### ### web page (www.amanda.org). ### ### ### ### !!! WARNING !!! !!! WARNING !!! !!! WARNING !!! !!! WARNING !!! ### # # amanda.conf - sample Amanda configuration file. This started off life as # the actual config file in use at CS.UMD.EDU. # # If your configuration is called, say, "csd", then this file normally goes # in /usr/local/etc/amanda/csd/amanda.conf. # org "Matrix"# your organization name for reports mailto "[EMAIL PROTECTED]" # space separated list of operators at your site dumpuser "backup" # the user to run dumps under inparallel 4# maximum dumpers that will run in parallel (max 63) # this maximum can be increased at compile-time, # modifying MAX_DUMPERS in server-src/driverio.h netusage 600 Kbps # maximum net bandwidth for Amanda, in KB per sec dumpcycle 4 weeks # the number of days in the normal dump cycle runspercycle 20 # the number of amdump runs in dumpcycle days # (4 weeks * 5 amdump runs per week -- just weekdays) tapecycle 25 tapes # the number of tapes in rotation # 4 weeks (dumpcycle) times 5 tapes per week (just # the weekdays) plus a few to handle errors that # need amflush and so we do not overwrite the full # backups performed at the beginning of the previous # cycle ### ### ### # WARNING: don't use `inf' for tapecycle, it's broken! ### ### ### bumpsize 20 Mb # minimum savings (threshold) to bump level 1 -> 2 bumpdays 1 # minimum days at each level bumpmult 4 # threshold = bumpsize * bumpmult^(level-1) etimeout 300# number of seconds per filesystem for estimates. #etimeout -600 # total number of seconds for estimates. # a positive number will be multiplied by the number of filesystems on # each host; a negative number will be taken as an absolute total time-out. # The default is 5 minutes per filesystem. dtimeout 1800 # number of idle seconds before a dump is aborted. ctimeout 30 # maximum number of seconds that amcheck waits # for each client host tapebufs 20 # A positive integer telling taper how many 32k buffers to allocate. # WARNING! If this is set too high, taper will not be able to allocate # the memory and will die. The default is 20 (640k). # Specify tape device and/or tape changer. If you don't have a tape # changer, and you don't want to use more than one tape per run of # amdump, just comment out the definition of tpchanger. # Some tape changers require tapedev to be defined; others will use # their own tape device selection mechanism. Some use a separate tape # changer device (changerdev), others will simply ignore this # parameter. Some rely on a configuration file (changerfile) to # obtain more information about tape devices, number of slots, etc; # others just need to store some data in files, whose names will start # with changerfile. For more information about individual tape # changers, read docs/TAPE.CHANGERS. # At most one changerfile entry must be defined; select the most # appropriate one for your configuration. If you select man-changer, # keep the first one; if you decide not to use a tape changer, you may # comment them all out. runtapes 1 # number of tapes to be used in a single run of amdump #tpchanger "chg-manual" # the tape-changer glue script tapedev "/dev/ht0" # the no-rewind tape device to be used #rawtapedev "/dev/ht0" # the raw device to be used (ftape only) #changerfile "/usr/adm/amanda/DailySet1/changer" #changerfile "/usr/adm/amanda/DailySet1/changer-status" #changerfile "/usr/local/etc/amanda/DailySet1/changer.conf" #changerdev "/dev/null" tapetype STT8000A
RE: disk offline - runtar as root
I guess it must be a check thats compiled in? Try recompiling, if I remember (its been a while...) its something like --with-amanda-user=amanda [or whichever user you are using] --with-amanda-group=sys [in your case] Best to check this in the docs though! -Original Message- From: Jonathan Murray [mailto:[EMAIL PROTECTED]] Sent: 06 June 2002 18:25 To: Spicer, Kevin Cc: [EMAIL PROTECTED] Subject: Re: disk offline - runtar as root borzoi 63# pwd /usr/freeware/libexec -rwsr-x---1 root sys21876 May 31 17:36 runtar /etc/group: borzoi 6% cat /etc/group sys::0:root,bin,sys,adm,amanda root::0:root daemon::1:root,daemon bin::2:root,bin,daemon adm::3:root,adm,daemon mail::4:root uucp::5:uucp rje::8: lp:*:9: nuucp::10:nuucp user::20:amanda CMWlogin::994: other::995: demos:*:997: guest:*:998: nobody:*:60001: runtar attempt as user amanda: borzoi 8% whoami amanda borzoi 7% ./runtar runtar: error [must be invoked by root] How do did you get runtar: error [must be invoked by amanda] ? thank you, -Jonathan Murray Spicer, Kevin wrote: > cd /usr/local/libexec > chown root:amanda runtar > chmod 4750 runtar > > assuming runtar is in usr/local/libexec and that the amanda user is in the amanda >group... > > But... I suspect that you haven't got runtar in the right group (or the amanda user >in the right group) as your message suggests runtar is generating the error. > When try to invoke runtar on my system (as myself) I get > runtar: error [must be invoked by amanda] > I don't know whether this check is hardwired in at compile time - in which case you >may need to recompile? > > -Original Message- > From: Jonathan Murray [mailto:[EMAIL PROTECTED]] > Sent: 06 June 2002 15:25 > To: Jonathan Murray > Cc: [EMAIL PROTECTED] > Subject: disk offline - runtar as root > > > It appears that the client isn't running runtar as root. Does anyone > know how to force the client to run runtar as root? > > Thanks, > > Jonathan Murray > > from report: > > FAILURE AND STRANGE DUMP SUMMARY: >borzoi /dev/dsk/dks0d2s7 lev 0 FAILED [disk /dev/dsk/dks0d2s7 > offline on borzoi?] >borzoi /dev/dsk/dks0d1s0 lev 0 FAILED [disk /dev/dsk/dks0d1s0 > offline on borzoi?] > > > > on client: > > calculating for amname '/dev/dsk/dks0d2s7', dirname '/borzoi' > sendsize: getting size via gnutar for /dev/dsk/dks0d2s7 level 0 > sendsize: missing exclude list file "/usr/local/lib/amanda/exclude.gtar" > discarded > sendsize: spawning /usr/freeware/libexec/runtar in pipeline > sendsize: argument list: /usr/freeware/bin/tar --create --file /dev/null > --directory /borzoi --one-file-system --listed-incremental > /var/amanda/gnutar-lists/borzoi_dev_dsk_dks0d2s7_0.new --sparse > --ignore-failed-read --totals . > runtar: error [must be invoked by root] > > >
