Re: is my dumpcycle conf ok ?
On Apr 2, 2001, verdon <[EMAIL PROTECTED]> wrote:
>> >I wanted to perform a FULL dump each sunday during 10 weeks
>>
>> Jason is correct that you want "dumpcycle 0" to force the full dumps.
>>
>> I just wanted to add that if these clients are also being backed up
>> with another configuration (e.g. daily), you want to add "record no"
>> to the dumptype so the two do not get crossed up.
> i probably didn't have this problem because the daily backup are onto on
> cycle which exclude the week-end (i'm doing full backup during the
> week-end)
Nope. You just failed to notice you have a problem. When doing a
full restore, you may notice restore may complain that a level 2
backup done on Monday is not based on the level 1 ran on Friday, but
on the archive full backup done on Sunday.
--
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
Re: Failure on W2k client
Ummm! > > >added interface ip=128.84.247.9 bcast=128.84.247.255 nmask=255.255.255.0 > > >added interface ip=128.84.247.9 bcast=128.84.247.255 nmask=255.255.255.0 > > >added interface ip=128.84.247.9 bcast=128.84.247.255 nmask=255.255.255.0 > > >added interface ip=128.84.247.9 bcast=128.84.247.255 nmask=255.255.255.0 > > >read_socket_with_timeout: timeout read. read error = Connection reset by peer. > > >session setup failed: code 0 That's Samba doing a broadcast to find a particular machine. I've noticed that amanda-2.4.2p1 doesn't like broadcasts at all and will fail dismally even though smbclient will cope. You either need to: * setup a "wins" server on the samba machine * setup /etc/smb.conf on the samba machine to point at your "wins" server Now, I can't explain this very well but Samba, by default, will lookup DNS, wins and then broadcast. You use "wins" if you want the SMB protocol to work across a subnet; because you can't broadcast across a subnet you need a special server to harvest the other subnet's information. If your local Samba can't find the machine you want locally, or via a local wins server, it will start to broadcast. Eventually one of your wins servers will respond or it will timeout. I've noticed that Amanda doesn't like this broadcast behaviour at all and will fail despite the fact that smbclient '\\OTHERMACHINE\Share' will eventually work. In my smb.conf I have: wins server = winsserver.mydomain.com.au wins support = No name resolve order = wins bcast host lmhosts Amongst other things DSL -- There's a sad face in the mirror And I'm sad to say it's me Like a ghost up in the attic Only love can set met free...
unsubscribe
unsubscribe
Re: Failure on W2k client
As someone with historic but aging knowledge of the installation in question, I'll add a couple of observations from the "for what it's worth" dept... The first thing that raises my eyebrows about this is that the address 128.84.247.9 belongs to an ethernet switch. I don't know if you changed it before posting in order to obfuscate the details for your own protection, or if that's really what was in the log file, but if it's really what's in the log file I would want to track down how amanda came up with this address. It can't be right. Secondly you said the amanda server is named "herman", but you don't have herman registered in your DNS. You didn't say who the Samba intermediary is but I'm jumping to the conclusion that you're using "herman" for that function, too. Same comment as above, perhaps you changed the name in your message to protect the innocent. I imagine the Samba intermediary machine is going to have to exist in the DNS in order for Samba backups to work properly. -Mitch On Mon, 2 Apr 2001, John R. Jackson wrote: > >we are getting this intermittent error: > >... > >added interface ip=128.84.247.9 bcast=128.84.247.255 nmask=255.255.255.0 > >added interface ip=128.84.247.9 bcast=128.84.247.255 nmask=255.255.255.0 > >added interface ip=128.84.247.9 bcast=128.84.247.255 nmask=255.255.255.0 > >added interface ip=128.84.247.9 bcast=128.84.247.255 nmask=255.255.255.0 > >read_socket_with_timeout: timeout read. read error = Connection reset by peer. > >session setup failed: code 0 > > > >The multiple "added interface" messages we don't see in any > >successful transactions. > >. > >Repeatedly running smbclient by hand: ... > >we see only single interface messages, no errors or timeouts. We do > >notice that the response is instantaneous. > > > >Is it possible that the quick response is confusing sendsize? > > I doubt it. > > The only thing I can guess is that at the time Amanda runs, something > else was going on with that machine (or its network connection, etc) > and Samba really couldn't talk to it. If you had tried your test right > then, I'll bet it would have acted exactly like what Amanda reported. > > I didn't look at the Samba code, but as a guess, the multiple "added > interface" lines are retries by them while trying to set up the > connection, and they eventually gave up. > > >We are backing up other NT and W2k clients successfully and only see > >this error on this client. > > That would also seem to imply something odd about this client. > > You might ask on the Samba mailing lists. I doubt it's a problem with > their code, but they might have a better idea of what it means and if > there are possible workarounds (longer timeouts, more retries, etc). > > >hurf > > John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED] >
Re: ATL L500
>... Durring boot up its detected as 2 tape devices, dev/st0 and >dev/st1. I tried running tapetype, and it complained about not being able to >rewind. can anyone shed some light on my problems? Did it say it could not rewind, or that you should be using a no-rewind device name (please post actual error messages)? Those are not the right device names for Amanda to use. You need to use /dev/nst0 and /dev/nst1. >Tom Priore John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
ATL L500
Does anyone have experice setting up and ATL L500 tape changer with amanda and linux. Durring boot up its detected as 2 tape devices, dev/st0 and dev/st1. I tried running tapetype, and it complained about not being able to rewind. can anyone shed some light on my problems? Tom Priore
Re: Failure on W2k client
>we are getting this intermittent error: >... >added interface ip=128.84.247.9 bcast=128.84.247.255 nmask=255.255.255.0 >added interface ip=128.84.247.9 bcast=128.84.247.255 nmask=255.255.255.0 >added interface ip=128.84.247.9 bcast=128.84.247.255 nmask=255.255.255.0 >added interface ip=128.84.247.9 bcast=128.84.247.255 nmask=255.255.255.0 >read_socket_with_timeout: timeout read. read error = Connection reset by peer. >session setup failed: code 0 > >The multiple "added interface" messages we don't see in any >successful transactions. >. >Repeatedly running smbclient by hand: ... >we see only single interface messages, no errors or timeouts. We do >notice that the response is instantaneous. > >Is it possible that the quick response is confusing sendsize? I doubt it. The only thing I can guess is that at the time Amanda runs, something else was going on with that machine (or its network connection, etc) and Samba really couldn't talk to it. If you had tried your test right then, I'll bet it would have acted exactly like what Amanda reported. I didn't look at the Samba code, but as a guess, the multiple "added interface" lines are retries by them while trying to set up the connection, and they eventually gave up. >We are backing up other NT and W2k clients successfully and only see >this error on this client. That would also seem to imply something odd about this client. You might ask on the Samba mailing lists. I doubt it's a problem with their code, but they might have a better idea of what it means and if there are possible workarounds (longer timeouts, more retries, etc). >hurf John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: amanda problems
>? gtar: time_t value 18446744071597657311 too large (max=68719476735) >... >Last night I got this error but I' am not sure what does it mean? It means you have several files out there with "negative" times in them. For instance, 18446744071597657311 translates to 0x,0x821f0cdf. That, in turn, means someone set a file time to either Jan 29, 1903, or about Feb 16, 2039 (if I did the math right). GNU tar apparently did not translate these values properly, which may, in turn, mean your OS didn't. It has room in the tar header field for them when considered as unsigned. So I suspect you're going to have to talk to the GNU tar folk about this. Be sure to tell them what version you're using and what OS. In the meantime, about the only thing I can suggest is that you find the files with the bogus values and change them (e.g. with "touch"). I'm not sure exactly how to find them, but you might try a GNU tar run to /dev/null with --verbose and hope that the file name comes out with the error message. If that doesn't work, try it to a pipe to cat to /dev/null (GNU tar looks for output going to /dev/null and shortstops some processing). >Sandra John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: Cannot stat NFS mount
>? gtar: Cannot stat ./mnt/BORA: Permission denied >... >we woud know if there is >something to to (other than an exclude-list, which we intend look for) to >avoid errors from amanda when NFS mounts go into troubles. Which is the mount point, /mnt or /mnt/BORA? If it's /mnt, then I don't know why GNU tar tried to go any further. If it's BORA, then there probably isn't anything you can do other than set up an exclude list. GNU tar has to stat() the directory/mount point to notice that it is on a different file system and thus should stop descent, and the stat() operation is probably the one throwing the error. I'm not even sure an exclude list will work. It depends on how GNU tar decides to not keep descending into a directory tree. You may need to talk to those folks rather than the Amanda group about this. >Alessio. John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: AIX rs6000 and Exabyte 10h changer
>I have an rs6000 using AIX 4.1.4 and a exabyte 10h tape changer >library. I am trying to configure these for use with AMANDA. >... >How can I configure the library for use with AMANDA? > >- Do I need IBM microcode? I doubt it, but you never know with them. >- Do I need jukebox software? Possibly. >- Does AMANDA have a driver that I can configure >so that the existence of the changer shows up with lscfg? No. Amanda doesn't do drivers. It expects you to have one that it can then use. However, the chg-scsi Amanda changer that comes with 2.4.2 purports to know how to deal with AIX scsi changers, so that's where I would start. It looks like it works with entries of the form /dev/scsi0. Do you have something like that? John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: Problem with host name lookup
>ERROR: dilston: [addr 149.135.66.137: hostname lookup failed] >... >... As you will notice, amanda fails with a hostname lookup Specifically, it says that the client tried to do an IP->host lookup of 149.135.66.137 and that failed. Note that it's the client with the problem, not the server, so concentrate your efforts there. >but nslookup and ping both work fine to the host I am trying to get too. As above, this is the wrong way around. You need to do those tests on the client and see if you can get back to the server. Note also that nslookup and ping are mostly irrelevant. They may or may not do the same lookups as Amanda. See: ftp://gandalf.cc.purdue.edu/pub/amanda/gethostby*.c >David Logan John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: amdump to RH7 client
>Try to backup a RH7 client named tux - no luck. >... >WARNING: tux: selfcheck request timed out. Host down? Have you gone through the items in the FAQ at www.amanda.org? This is a very common first problem to have. In particular, I seem to recall the xinetd config files with the RH7 RPM's were broken. >Frank Nardis John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: Tape Host
>Is there something special to do to the Host machine to inform >AMANDA that it is the host? I've configured everything, as nearly as I >can figure, correctly but obviously haven't since I'm still getting host >down when running amcheck. ... Have you read the FAQ at www.amanda.org? This is a very common first problem to have with Amanda and it is covered in there. If you still cannot get it to work, please post back here what you tried and what the results were. >What should be entered to either amanda.conf >or disklist to say that this is the host machine. Your problem is probably that inetd/xinetd have not been set up to run amandad properly. Again, it's covered in the FAQ. >Andrew R. Falanga John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Failure on W2k client
Hi Folks, Backing up shared folders (not full disk) a PC (Dell 420 dual 1ghz/W2k/sp1/15k-rpm UW scsi), we are getting this intermittent error: herman//rodney/workII lev 0 FAILED [disk //rodney/workII offline on herman?] "herman" is the amanda system ( FreeBSD 4.2-STABLE/"Amanda-2.4.2"/smbclient 2.0.7 ) this seems to be initiated by an error in sendsize (from sendsize.debug) sendsize: argument list: "smbclient" "\\rodney\workII" "-d" "0"\ "-U" "backup_user%secret" "-E" "-W" "PC-GROUP" "-c" "archive 0;recurse;du" added interface ip=128.84.247.9 bcast=128.84.247.255 nmask=255.255.255.0 added interface ip=128.84.247.9 bcast=128.84.247.255 nmask=255.255.255.0 added interface ip=128.84.247.9 bcast=128.84.247.255 nmask=255.255.255.0 added interface ip=128.84.247.9 bcast=128.84.247.255 nmask=255.255.255.0 read_socket_with_timeout: timeout read. read error = Connection reset by peer. session setup failed: code 0 The multiple "added interface" messages we don't see in any successful transactions. . Repeatedly running smbclient by hand: `smbclient '\\rodney\workII' -U backup_user%secret -d 0 -E -W DOMAIN -c 'archive 0;recurse;du' we see only single interface messages, no errors or timeouts. We do notice that the response is instantaneous. Is it possible that the quick response is confusing sendsize? We are backing up other NT and W2k clients successfully and only see this error on this client. any help appreciated. thanks, hurf Hurf Sheldon Dir. Research Systems Program of Computer Graphics 580 Rhodes Hall, Hoy Rd. Cornell University Ithaca, N.Y. 14853 voice:607 255 6713 fax:607 255 0806 email: [EMAIL PROTECTED] http://www.graphics.cornell.edu/~hurf/
Re: putting disklist entries on 'standby'
>What's the recommended procedure for temporarily removing a disklist entry? >... My solution is to just comment out the disklist entry, but I'm >not sure what effect that has on indexing, amrecover, etc. That's what I do. You won't be able to do an amrecover while they are commented out (as I recall), so you may need to swap them in and out if that comes up. When the machine comes back on line, Amanda will see that it has been a long time since the last level 0 and promote things as needed (or you can use "amadmin force"), which may put you out of balance for a couple of cycles, but it will get straightened out. >Carey John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: amdump
>sendsize: debug 1 pid 12301 ruid 33 euid 33 ... >runtar: error [must be invoked by operator] >... > >What on earth does that mean??! What on earth do I do? This says Amanda was built with "operator" as the Amanda user, but that amandad (and then sendbackup and then runtar) is being run as some other user from inetd/xinetd. Furthermore, the first line says they are running as uid 33, whoever that is. So, you either need to change inetd.conf or the xinetd config file to run amandad as "operator" (and get the config file reread), or you need to rebuild Amanda with --with-user=. John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
RE: Unable to install Amanda
> configure: error: *** --with-user=USER is missing > Any corrective suggestions are welcomed. Read the documentation that comes with source - docs/INSTALL. Amanda needs a user defined, ie --with-user=amanda. -Ben
RE: Unable to install Amanda
Please read the installation instructions in docs/INSTALL very carefully,
especially sections 1.1.F and 1.1.I.a. AMANDA requires several parameters
for configuration, including the user and group to run under.
-Original Message-
From: Tru64 User [mailto:[EMAIL PROTECTED]]
Sent: Monday, April 02, 2001 4:06 PM
To: [EMAIL PROTECTED]
Subject: Unable to install Amanda
Hi,
New to Amanda.
Trying to isntall it on tru64 Unix, getting error in
first step (configure) as follows:
$configure
loading cache ./config.cache
checking host system type... alphaev56-dec-osf4.0g
checking target system type... alphaev56-dec-osf4.0g
checking build system type... alphaev56-dec-osf4.0g
checking cached system tuple... ok
checking for a BSD compatible install...
/opt/gnu/bin/install -c
checking whether build environment is sane... yes
checking for mawk... no
checking for gawk... gawk
checking whether make sets ${MAKE}... yes
checking for working aclocal... found
checking for working autoconf... found
checking for working automake... found
checking for working autoheader... found
checking for working makeinfo... found
checking for gnutar... no
checking for gtar... gtar
configure: error: *** --with-user=USER is missing
$
Any corrective suggestions are welcomed.
=
__
Do You Yahoo!?
Get email at your own domain with Yahoo! Mail.
http://personal.mail.yahoo.com/?.refer=text
Re: dumper stalling while taper is running
>... I *believe* I'm seeing a situation where while >running amdump, a check with amstatus shows that while one of my large >fs's is taping from holding disk, the fs's that have not dumped yet are >NOT being dumped even though I have plenty holding disk available, then >after the tape job completes the dump starts again. ... First, you should never assume amstatus is telling the whole truth. It only looks at the amdump file, which is not locked and messages can get garbled. Having said that, I'd start looking at the file by hand near the time of the taper start for the big fs and see what it says is going on that it cannot start another dump. >I think John had a >perl script that would take an amdump files and convert the time stamps? ftp://gandalf.cc.purdue.edu/pub/amanda/amdumpts >George Kelbley John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: Don't have tape drive
>John Jackson has developed a function that lets you pretend that a disk >drive is a tape device. This is in one of the latest beta releases. ... Actually, it's not in any of the releases. It's only in the CVS source tree as branch amanda-242-tapeio. >DSL John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Unable to install Amanda
Hi,
New to Amanda.
Trying to isntall it on tru64 Unix, getting error in
first step (configure) as follows:
$configure
loading cache ./config.cache
checking host system type... alphaev56-dec-osf4.0g
checking target system type... alphaev56-dec-osf4.0g
checking build system type... alphaev56-dec-osf4.0g
checking cached system tuple... ok
checking for a BSD compatible install...
/opt/gnu/bin/install -c
checking whether build environment is sane... yes
checking for mawk... no
checking for gawk... gawk
checking whether make sets ${MAKE}... yes
checking for working aclocal... found
checking for working autoconf... found
checking for working automake... found
checking for working autoheader... found
checking for working makeinfo... found
checking for gnutar... no
checking for gtar... gtar
configure: error: *** --with-user=USER is missing
$
Any corrective suggestions are welcomed.
=
__
Do You Yahoo!?
Get email at your own domain with Yahoo! Mail.
http://personal.mail.yahoo.com/?.refer=text
dumper stalling while taper is running
I believe someone posted a similar problem a while back but I couldn't find it in the archive. I *believe* I'm seeing a situation where while running amdump, a check with amstatus shows that while one of my large fs's is taping from holding disk, the fs's that have not dumped yet are NOT being dumped even though I have plenty holding disk available, then after the tape job completes the dump starts again. I think John had a perl script that would take an amdump files and convert the time stamps? -- George Kelbley System Support Group Computer Science Department University of New Mexico 505-277-6502Fax: 505-277-6927
Re: amdump to RH7 client
Verdon, Check you disklist file on the server. With RH 7.0 they changed it so that to access the disks on the client you specify the MOUNT POINT in the dislist instead of the disk-device. EG: use /usr/local instead of hda1 or /dev/hda1. I just had this same problem and that is what fixed it. On Mon, 02 Apr 2001, you wrote: > you probably have to check .rhosts and .amandahosts on your client > side... > > you said you have used a rpm ?? > which user and group did the amandaserver use to perform backup? > > > "Nardis, Frank" wrote: > > > > Hello, > > > > Got amanda running on a RH6.2 tape server - able to dump tape server. > > > > Try to backup a RH7 client named tux - no luck. > > > > Output of amcheck and amdump below > > > > Any help greatly appreciated. > > > > PS - both server and client software loaded via RPMS - not built from > > tarball. > > > > bash$ amcheck DailySet1 > > > > Amanda Tape Server Host Check > > - > > /home/amanda/dumps: 13186700 KB disk space available, that's plenty. > > NOTE: skipping tape-writable test. > > Tape DailySet101 label ok. > > Server check took 0.050 seconds. > > > > Amanda Backup Client Hosts Check > > > > WARNING: tux: selfcheck request timed out. Host down? > > Client check: 1 host checked in 29.999 seconds, 1 problem found. > > > > (brought to you by Amanda 2.4.1p1) > > > > > > -- > > bash$ amdump DailySet1 > > > > These dumps were to tape DailySet101. > > Tonight's dumps should go onto 1 tape: a new tape. > > > > FAILURE AND STRANGE DUMP SUMMARY: > > tuxmd0 lev 0 FAILED [Request to tux timed out.] > > tuxmd3 lev 0 FAILED [Request to tux timed out.] > > STATISTICS: > > Total Full Daily > > > > Dump Time (hrs:min)0:01 0:00 0:00 (0:00 start, 0:00 > > idle) > > 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: Adding new disk tux:md3. > > planner: Adding new disk tux:md0. > > driver: WARNING: got empty schedule from planner > > taper: tape DailySet101 kb 0 fm 0 [OK] > > > > DUMP SUMMARY:-- > > -- -- > > tux md00 FAILED > > > > tux md30 FAILED > > > > > > (brought to you by Amanda version 2.4.1p1) > > > > Frank Nardis > > Trend Consulting Services Inc. http://www.trendcs.com > > 35353 Curtis Blvd. Suite 201 > > Eastlake,OH. 44095-4029 > > Tel: 440.942.4040 x221 Fax: 440.942.4848 > > PGP key - http://www.keyserver.net > > mailto:[EMAIL PROTECTED]
putting disklist entries on 'standby'
What's the recommended procedure for temporarily removing a disklist entry? Say, for example, a server is down for a few days, and you want to not back it up, but plan to resume backups later. 'amadmin delete' seems a bit cruel for that. My solution is to just comment out the disklist entry, but I'm not sure what effect that has on indexing, amrecover, etc. thanks in advance for any help, Carey Carey Jung IT Freedom [EMAIL PROTECTED] 512.419.0070, fax 419.0080
Tape Host
Ok, Is there something special to do to the Host machine to inform AMANDA that it is the host? I've configured everything, as nearly as I can figure, correctly but obviously haven't since I'm still getting host down when running amcheck. What should be entered to either amanda.conf or disklist to say that this is the host machine. -- Andrew R. Falanga, A+, CNA, CNE (NetWare 4 & 5) Network Engineer/Hostmaster Networks.Com, Inc.
Re: compiling error on a client...
verdon wrote: > > i'm actually installing amanda on a few server (redhat 6.2) "this is > probably why i'm always asking strange question" :) > > usually when running ./configure i get: > > checking disk device prefixes... /dev/ - /dev/ > checking whether posix fcntl locking works... (cached) yes > > but on one server i have the following error and compilation abort with > some error > > checking disk device prefixes... /dev/ - /dev/ > checking whether posix fcntl locking works... (cached) no > checking whether flock locking works... (cached) no > checking whether lockf locking works... (cached) no > checking whether lnlock locking works... (cached) no > configure: warning: *** No working file locking capability found! > configure: warning: *** Be VERY VERY careful. > > this server is running like the other: > redhat-6.2 > glibc-2.1.3-15 > glibc-devel-2.1.3-15 > > i have look in my kernel configuration for an optional "posix support" > that i would have not enable!?? but i didn't find anything about it > i just have change my kernel to 2.4.2 but this didn't change anything? > > I've look for similar error in amanda mailing list archives ...without > great success... You cannot run glibc-2.1.* with a 2.4 kernel. They are incompatible in a number of ways. Either downgrade the kernel to a 2.2 or upgrade glibc to a 2.2. In general, it isn't a good idea (unless you're a kernel hacker) to run anything more advanced than what appears in the appropriate updates directory on update.redhat.com. It surprises me more than a little bit that the system works well enough to do much of anything on it! Cheers, Marty -- Marty Shannon, RHCE, Independent Computing Consultant mailto:[EMAIL PROTECTED]
compiling error on a client...
i'm actually installing amanda on a few server (redhat 6.2) "this is probably why i'm always asking strange question" :) usually when running ./configure i get: checking disk device prefixes... /dev/ - /dev/ checking whether posix fcntl locking works... (cached) yes but on one server i have the following error and compilation abort with some error checking disk device prefixes... /dev/ - /dev/ checking whether posix fcntl locking works... (cached) no checking whether flock locking works... (cached) no checking whether lockf locking works... (cached) no checking whether lnlock locking works... (cached) no configure: warning: *** No working file locking capability found! configure: warning: *** Be VERY VERY careful. this server is running like the other: redhat-6.2 glibc-2.1.3-15 glibc-devel-2.1.3-15 i have look in my kernel configuration for an optional "posix support" that i would have not enable!?? but i didn't find anything about it i just have change my kernel to 2.4.2 but this didn't change anything? I've look for similar error in amanda mailing list archives ...without great success...
Re: amdump to RH7 client
you probably have to check .rhosts and .amandahosts on your client side... you said you have used a rpm ?? which user and group did the amandaserver use to perform backup? "Nardis, Frank" wrote: > > Hello, > > Got amanda running on a RH6.2 tape server - able to dump tape server. > > Try to backup a RH7 client named tux - no luck. > > Output of amcheck and amdump below > > Any help greatly appreciated. > > PS - both server and client software loaded via RPMS - not built from > tarball. > > bash$ amcheck DailySet1 > > Amanda Tape Server Host Check > - > /home/amanda/dumps: 13186700 KB disk space available, that's plenty. > NOTE: skipping tape-writable test. > Tape DailySet101 label ok. > Server check took 0.050 seconds. > > Amanda Backup Client Hosts Check > > WARNING: tux: selfcheck request timed out. Host down? > Client check: 1 host checked in 29.999 seconds, 1 problem found. > > (brought to you by Amanda 2.4.1p1) > > > -- > bash$ amdump DailySet1 > > These dumps were to tape DailySet101. > Tonight's dumps should go onto 1 tape: a new tape. > > FAILURE AND STRANGE DUMP SUMMARY: > tuxmd0 lev 0 FAILED [Request to tux timed out.] > tuxmd3 lev 0 FAILED [Request to tux timed out.] > STATISTICS: > Total Full Daily > > Dump Time (hrs:min)0:01 0:00 0:00 (0:00 start, 0:00 > idle) > 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: Adding new disk tux:md3. > planner: Adding new disk tux:md0. > driver: WARNING: got empty schedule from planner > taper: tape DailySet101 kb 0 fm 0 [OK] > > DUMP SUMMARY:-- > -- -- > tux md00 FAILED > > tux md30 FAILED > > > (brought to you by Amanda version 2.4.1p1) > > Frank Nardis > Trend Consulting Services Inc. http://www.trendcs.com > 35353 Curtis Blvd. Suite 201 > Eastlake,OH. 44095-4029 > Tel: 440.942.4040 x221 Fax: 440.942.4848 > PGP key - http://www.keyserver.net > mailto:[EMAIL PROTECTED]
amdump to RH7 client
Hello,
Got amanda running on a RH6.2 tape server - able to dump tape server.
Try to backup a RH7 client named tux - no luck.
Output of amcheck and amdump below
Any help greatly appreciated.
PS - both server and client software loaded via RPMS - not built from
tarball.
bash$ amcheck DailySet1
Amanda Tape Server Host Check
-
/home/amanda/dumps: 13186700 KB disk space available, that's plenty.
NOTE: skipping tape-writable test.
Tape DailySet101 label ok.
Server check took 0.050 seconds.
Amanda Backup Client Hosts Check
WARNING: tux: selfcheck request timed out. Host down?
Client check: 1 host checked in 29.999 seconds, 1 problem found.
(brought to you by Amanda 2.4.1p1)
--
bash$ amdump DailySet1
These dumps were to tape DailySet101.
Tonight's dumps should go onto 1 tape: a new tape.
FAILURE AND STRANGE DUMP SUMMARY:
tuxmd0 lev 0 FAILED [Request to tux timed out.]
tuxmd3 lev 0 FAILED [Request to tux timed out.]
STATISTICS:
Total Full Daily
Dump Time (hrs:min)0:01 0:00 0:00 (0:00 start, 0:00
idle)
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: Adding new disk tux:md3.
planner: Adding new disk tux:md0.
driver: WARNING: got empty schedule from planner
taper: tape DailySet101 kb 0 fm 0 [OK]
DUMP SUMMARY:--
-- --
tux md00 FAILED
tux md30 FAILED
(brought to you by Amanda version 2.4.1p1)
Frank Nardis
Trend Consulting Services Inc. http://www.trendcs.com
35353 Curtis Blvd. Suite 201
Eastlake,OH. 44095-4029
Tel: 440.942.4040 x221 Fax: 440.942.4848
PGP key - http://www.keyserver.net
mailto:[EMAIL PROTECTED]
AIX rs6000 and Exabyte 10h changer
Hello, I have an rs6000 using AIX 4.1.4 and a exabyte 10h tape changer library. I am trying to configure these for use with AMANDA. AIX recognizes the tape drive as rmt3 (scsi address =1) but I don't see any indication of the library unit on address =4. How can I configure the library for use with AMANDA? - Do I need IBM microcode? - Do I need jukebox software? - Does AMANDA have a driver that I can configure so that the existence of the changer shows up with lscfg? I have scoured the archives and visited exabyte.com and ibm.com and can't seem to find anything to get me past this. I know there are other commercial packages doing this, but they seem to have special drivers. I am a newbie to AMANDA and tape changers so any help is appreciated. Thanks!
amanda problems
Hi everybody:
Last night I got this error but I' am not sure what does it mean?
FAILURE AND STRANGE DUMP SUMMARY:
manray.tom /Local lev 5 FAILED [/usr/bin/gnutar returned 2]
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:14
Run Time (hrs:min) 1:46
Dump Time (hrs:min)2:04 1:37 0:27
Output Size (meg)1797.2 1571.4 225.8
Original Size (meg) 2987.1 2660.4 326.6
Avg Compressed Size (%)57.6 59.1 29.4
(level:#disks ...)
Filesystems Dumped 12 7 5 (1:1 2:2 3:2)
Avg Dump Rate (k/s) 246.6 275.9 141.8
Tape Time (hrs:min)0:00 0:00 0:00
Tape Size (meg) 0.00.00.0
Tape Used (%) 0.00.00.0
Filesystems Taped 0 0 0
Avg Tp Write Rate (k/s) -- -- --
FAILED AND STRANGE DUMP DETAILS:
/-- manray.tom /Local lev 5 FAILED [/usr/bin/gnutar returned 2]
sendbackup: start [manray.tomandandy.com:/Local level 5]
sendbackup: info BACKUP=/usr/bin/gnutar
sendbackup: info RECOVER_CMD=/usr/bin/gzip -dc |/usr/bin/gnutar -f... -
sendbackup: info COMPRESS_SUFFIX=.gz
sendbackup: info end
? gtar: time_t value 18446744071597657311 too large (max=68719476735)
? gtar: time_t value 18446744071595921983 too large (max=68719476735)
? gtar: time_t value 18446744071595921983 too large (max=68719476735)
? gtar: time_t value 18446744071595921983 too large (max=68719476735)
? gtar: time_t value 18446744071595921983 too large (max=68719476735)
? gtar: time_t value 18446744071595921983 too large (max=68719476735)
? gtar: time_t value 18446744071595921983 too large (max=68719476735)
? gtar: time_t value 18446744071595921983 too large (max=68719476735)
? gtar: time_t value 18446744071597649142 too large (max=68719476735)
? gtar: time_t value 18446744071595921983 too large (max=68719476735)
? gtar: time_t value 18446744071595921983 too large (max=68719476735)
? gtar: time_t value 18446744071595921983 too large (max=68719476735)
? gtar: time_t value 18446744071595921982 too large (max=68719476735)
? gtar: time_t value 18446744071595921983 too large (max=68719476735)
| Total bytes written: 1415976960
? gtar: Error exit delayed from previous errors
sendbackup: error [/usr/bin/gnutar returned 2]
\
NOTES:
planner: Incremental of miro.tomandandy.com:/Local bumped to level 2.
planner: Incremental of duchamp.tomandandy.com:/Local/Users bumped to
level 2.
planner: Full dump of magritte.tomandandy.com:/public promoted from 24
days ahead.
planner: Full dump of miro.tomandandy.com:/usr/local promoted from 24
days ahead.
planner: Full dump of whiteley.tomandandy.com:/usr/local promoted from
24 days ahead.
planner: Full dump of duchamp.tomandandy.com:/var/mail promoted from
26 days ahead.
planner: Full dump of magritte.tomandandy.com:/Local/Users promoted
from 26 days ahead.
planner: Full dump of duchamp.tomandandy.com:/tomandandy/usrlocal
promoted from 26 days ahead.
planner: Full dump of magritte.tomandandy.com:/usr/local promoted from
26 days ahead.
DUMP SUMMARY:
DUMPER STATSTAPER STATS
HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
-- -
duchamp.toma -ocal/Users 2 95230 36256 38.1 8:43 69.3 N/A N/A
duchamp.toma -y/usrlocal 0 108230 28096 26.0 4:38 101.0 N/A N/A
duchamp.toma /var/mail 0 47380 23232 49.0 3:09 122.7 N/A N/A
magritte.tom -ocal/Users 0 806390 628928 78.0 39:35 264.8 N/A N/A
magritte.tom /home 1 11170160 1.4 3:01 0.9 N/A N/A
magritte.tom /public 0 732140 568512 77.7 35:05 270.1 N/A N/A
magritte.tom /tomandandy 3 188160 188160 --8:19 377.2 N/A N/A
magritte.tom /usr/local 0 89910 26112 29.0 1:18 336.6 N/A N/A
manray.toman /Local 5 FAILED ---
miro.tomanda /Local 2 10900 2208 20.3 0:42 52.6 N/A N/A
miro.tomanda /usr/local 0 786910 282080 35.8 11:26 411.3 N/A N/A
whiteley.tom /Local 3 29020 4448 15.3 6:26 11.5 N/A N/A
whiteley.tom /usr/local 0 153320 52192 34.0 2:01 430.0 N/A N/A
(brought to you by Amanda version 2.4.2-19991216-beta1)
I checked and somebody got something similar but was with the user Id.
But in my case the problem is with the time_t value.
does anybody know anything about this?. I would really appreciate any
suggestion
thanks a lot
Sandra
amdump
Hi, I have got amanda to backup /etc on tape server [redhat 7]. However, when i try to back up /etc on another machine [redhat 6.2] I get the following error in the email: FAILURE AND STRANGE DUMP SUMMARY: 6.2machine /etc lev 0 FAILED [disk /etc offline on 6.2machine?] I read some of the earlier messages with the same problem, and thus read /tmp/amanda/sendsize.debug on machine6.2 which gives me: == sendsize: debug 1 pid 12301 ruid 33 euid 33 start time Mon Apr 2 14:14:32 2001 /usr/lib/amanda/sendsize: version 2.4.1p1 calculating for amname '/etc', dirname '/etc' sendsize: getting size via gnutar for /etc level 0 sendsize: missing exclude list file "/usr/local/lib/amanda/exclude.gtar" discarded sendsize: running "/usr/lib/amanda/runtar --create --directory /etc --listed-increment al /var/lib/amanda/gnutar-lists/ruby.webstar.co.uk_etc_0.new --sparse --one-file-syste m --ignore-failed-read --totals --file /dev/null ." runtar: error [must be invoked by operator] . (no size line match in above gnutar output) . sendsize: pid 12301 finish time Mon Apr 2 14:14:32 2001 What on earth does that mean??! What on earth do I do? Any help will be appreicated Thanks. [Please help!! My boss wants me to use Bru - but I am determined not to use commercial software!!]
Re: Can I rm if I don't want to amflush?
Steve! > Can I just remove the holding disk directories that were created? I don't > particularly want to flush these to tape, but I also don't want to break > anything. I wouldn't "just remove" them if I were you, especially if the dumps were incremental. If you remove them it's possible you'll develop "holes" in your backup system. It would be safest to send them to tape... DSL -- There's a sad face in the mirror And I'm sad to say it's me Like a ghost up in the attic Only love can set met free...
Can I rm if I don't want to amflush?
I accidently ran amdump a couple of times over the weekend (forgot to test for the day of week in my backup script...) which caused some dumps to be put on the holding disk (amreport said "cannot overwrite active tape... run amflush...") Can I just remove the holding disk directories that were created? I don't particularly want to flush these to tape, but I also don't want to break anything. Thanks Steve Woodcock
Re: extract data from holding-disk
Verdon! > i was wondering if it is possible to extract data from the holding disk > with amrecover ? "amrecover" will speak to whatever tape or holding disk happens to have the file or files you request. So the answer is, yes. > if it isn't is suppose i had to use amrestore? "amrestore" can take the name of a file. Furthermore you can also use the base tools (gzip, tar, restore and all)... I suggest you man amrecover and man amrestore for the full details :-) DSL -- There's a sad face in the mirror And I'm sad to say it's me Like a ghost up in the attic Only love can set met free...
extract data from holding-disk
hi all, i was wondering if it is possible to extract data from the holding disk with amrecover ? if it isn't is suppose i had to use amrestore?
Re: Don't have tape drive
Hi There! > Sorry for this easy question . I don't have tape drive , can I use > amanda to backup my system. John Jackson has developed a function that lets you pretend that a disk drive is a tape device. This is in one of the latest beta releases. If you don't want to do that it is possible to setup amanda to speak to a non-existent device which will cause it to continuously dump to a holding disk (I use /dev/haha if I ever do this - it suits my perverted sense of humour :-P)... DSL -- There's a sad face in the mirror And I'm sad to say it's me Like a ghost up in the attic Only love can set met free...
Don't have tape drive
Hello, Sorry for this easy question . I don't have tape drive , can I use amanda to backup my system. Sincerely, Damrongkiet
Cannot stat NFS mount
Here we are using Amanda 2.4.1p1 + gtar (1.12 with amanda patches) to backup all our Linux (and windows) systems. The following messages comes (on more than one system) from amanda when something goes wrong with NFS: /-- breeze / lev 1 FAILED [/bin/gtar returned 2] sendbackup: start [breeze:/ level 1] sendbackup: info BACKUP=/bin/gtar sendbackup: info RECOVER_CMD=/bin/gzip -dc |/bin/gtar -f... - sendbackup: info COMPRESS_SUFFIX=.gz sendbackup: info end ? gtar: Cannot stat ./mnt/BORA: Permission denied | Total bytes written: 169922560 ? gtar: Error exit delayed from previous errors sendbackup: error [/bin/gtar returned 2] \ We know that gtar uses the only-one-file-system flag so amanda does not backup NFS mounted partitions (right!), but we woud know if there is something to to (other than an exclude-list, which we intend look for) to avoid errors from amanda when NFS mounts go into troubles. Thanks in advance for your help, Alessio. +---+ | Alessio Brezigar | | ARPA F-VG - OSMER | | v. Carso, 3 - loc. Scodovacca | | 33052 Cervignano d.F. (UD)| | ITALY | | Tel: +39-0431-382460 | | Fax: +39-0431-382400 | | e-mail: [EMAIL PROTECTED] | +---+
Re: is my dumpcycle conf ok ?
> >I wanted to perform a FULL dump each sunday during 10 weeks > > Jason is correct that you want "dumpcycle 0" to force the full dumps. > > I just wanted to add that if these clients are also being backed up > with another configuration (e.g. daily), you want to add "record no" > to the dumptype so the two do not get crossed up. i probably didn't have this problem because the daily backup are onto on cycle which exclude the week-end (i'm doing full backup during the week-end) > > Unless there are other things going on here you haven't explained > (like why you're forcing full dumps on a specific day, which is very > un-Amanda-like). you have right this is un-amanda-like, i force full dump because i am able to store all my data onto one tape (DLT IV 40GB) Noone is working during the week-end, and i have to take and store some "snapshost" for 6 mounth > > >Pierre-Yves VERDON > > John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: install-problems
> Hi all ,
>
> i tried to install amanda-2.4.2p1 but it failed.Don't know why,here's
> the output of ./configure :
>
> loading cache ./config.cache
> checking host system type... i586-pc-linux-gnu
> checking target system type... i586-pc-linux-gnu
> checking build system type... i586-pc-linux-gnu
> checking cached system tuple... ok
> checking for a BSD compatible install... /usr/bin/ginstall -c
> checking whether build environment is sane... yes
> checking for mawk... no
> checking for gawk... gawk
> checking whether make sets ${MAKE}... yes
> checking for working aclocal... missing
> checking for working autoconf... missing
> checking for working automake... missing
> checking for working autoheader... missing
> checking for working makeinfo... found
> checking for gnutar... no
> checking for gtar... gtar
> configure: error: *** --with-user=USER is missing
>
you had to read the INSTALL documentation before installing amanda
any way, her is your answer:
./configure --prefix=/your/directory --with-user=amanda_user
--with-group=amanda_group
