Re: Problems with big disklist file
snip huge amount of data If you actually READ what Amanda said, it's not complaining about the length of your disklist (1). It's getting a badly formatted response; I'm not sure why. Try checking the debug files on that machine in /tmp/amanda. DSL (1) grumpy=on How does one interpret this: mpe-3. /sistemas/folha/folhawindows/EBE lev 0 FAILED [badly formatted response from mpe-3.holding] As something wrong with a disklist? /grumpy
Re:
Chandra! server --with-user=(username) --with-gorup=(groupname). Then installation went through the rigourmole but couldn't find flex but gave up when it couldn't find lex. Can someone shine me shine light as to why this crashed. An actual posting of the error would help, but it probably needs flex or lex to compile. DSL -- MegaHAL: Linuxsa is not incorporated. User:Can an incorporated association send out a press release? MegaHAL: Linuxsa is a religion. - Quoting megahal (download: http://megahal.sourceforge.net/)
Re: Raid and Amanda
Oh? If you use tar (as opposed to dump) as the low-level utility, you can use a single amanda config, with a line in the disklist for each 10G subdirectory. I didn't know one could do that. How? DSL -- ACCUSATION: David Newall, you have not read your Microsoft Manual REPLY: No I haven't (quoting David Newall with permission)
Re: FreeBSD 4.3/inetd failing
Hang on a moment here. What we should be thinking is that someone thinks there should be a cross reference to this question in the FAQ We all categorise things differently to each other so what might seem like a sensible place for a question to you, may not be sensible to the next person... Put this in a FAQ somewhere! It already is. In: http://amanda.sourceforge.net/fom-serve/cache/140.html it says: If you are using a fire wall or TCP wrappers, make sure it is set up to allow the amanda service in to the client from the server. DSL
Re: New to Amanda, almost got it working...
Tyrone! I've created an user called amanda and a group called backup on the client and server machines. The amanda user is in the disk group as a secondary group on the client machine. What am I doing wrong? If you know of any source online where I can find the answer? Thanks in advance. a) does /dev/sdb1 exist? b) what does ls -l /dev/sdb1 tell you? c) are you certain that either user amanda or group backup can access /dev/sdb1? DSL -- Dodos are birds that are extinct - Quoted by D.S.L. 16 April 2001
Re: Linus Torvald's opinion on Dump.
sigh (*) Dump may work fine for you a thousand times. But it _will_ fail under the right circumstances. And there is nothing you can do about it. Let's generalise: [any program and anything] may work for you a thousand times. Bit it _will_ fail under the right circumstances. And there is nothing you can do about it. Now, would you also like to know the sky is blue and water is wet...or that the ugly duckling was actually a cygnet. Or that geese can fly, coke is blakc and McDonalds is an extraordinarily large fast food chain. DSL -- Dodos are birds that are extinct - Quoted by D.S.L. 16 April 2001
Re: Failure on W2k client
Todd! Marty says his samba setup works, but because of the fallback from wins to broadcast the lookup takes longer than amanda is willing to wait. Amanda times out and as far as amanda is concerned, smbclient failed. I'm not even sure what the implications of this are or how to make it work more efficiently, I'm just interpreting what he stated. Marty, is this correct? That is correct. However I said it, not Marty as you've already noted. All I'm saying (in my own obtuse way) is that it appears "weird" that amanda/smbclient don't always get along with each other. At the moment it's going to be easier to work around this "smbclient" behaviour because this version of smbclient is going to be in production for a reasonable time yet. Simply pointing out that "it's Samba's fault" isn't at all helpful even if it is true. Telling someone that "it's in the FAQ" when they've taken the time to attempt to help someone on the list isn't at all helpful even if the answer is in the FAQ. If you're going to tell people that it's in the FAQ or to read a manual you really should post a URL or some sort of indicator where the FAQ or manual is... I don't think I need to continue this thread any further; I'll just go along and help out where I can. If some people notice that I'm repeating the FAQ at http://www.amanda.org/ then so be it. They can stay silent... 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...
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...
Re: Failure on W2k client
The error I see is: "Host is down or invalid password" Essentially my guess is that Amanda via smbclient attempts to use a local wins server to resolve the Netbios name which didn't work because I didn't have a wins server configured. Hence, rather than wait for the broadcast to function (it can take up to 45 seconds on my systems to do so) it just decides the host is down. When running on broadcast, a packet trace will show at least one negative smb response before manages to resolve the machine I'm backing up. Huh? How can Amanda fail and smbclient work when Amanda is doing nothing more than call smbclient? See above. 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...
Re: Failure on W2k client
Marty! I suggest you put your asbestos, flame resistant suit on... Again: THIS IS NOT AMANDA'S FAULT! IT IS SMBCLIENT'S FAULT! You obviously cannot understand what I am saying, or you have not followed this thread. If you cannot understand English I will have this translated into any other language that I have a character set for: SMBCLIENT CAN CONTACT MY WINDOWS 2000 SERVER. IT DOES NOT FAIL. IT WORKS VIA BROADCAST AND AMANDA FAILS TO SEE THAT IT WORKS. Or to reword this: SAMBA IS ABLE TO CONTACT MY WINDOWS 2000 SERVER; SMBCLIENT CAN CONTACT IT. HOWEVER, IT DOES THIS VIA BROADCAST AND AMANDA FAILS. As far as I'm concerned SMB is working correctly. It is setup to use wins, wins fails and it therefore contacts my Windows 2000 server by broadcast and connects. Perfectly. So how is it smbclient's fault when smbclient works? I can't understand your English... DSL
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...
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...
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...
Re: Samba Report
Hi There! I have the 2.4.2 sources and pulled down the latest patch for 2.4.2. Does it fail when you use amcheck? What's in /tmp/amanda/selfcheck*debug on the Samba machine? No. I assume the Samba machine is running Amanda 2.4.2+? That's where it counts, not on the tape server. Hmmm My tape server is the samba machine. It needs to talk to my wins server, but smbclient is called locally. Therefore I think my samba server is using 2.4.2p1...I assure you that: //NAME/directory user%password Doesn't work for me... DSL -- And though you turn from me To glance behind The Phantom of the Opera is there... Inside your mind!
Re: Samba Report
Hmmm! Amanda is running: sendsize.debug:sendsize: spawning "/usr/bin/smbclient" in pipeline sendsize.debug:sendsize: argument list: "smbclient" "\\THESHARE\thedirectory" "the_password" "-d" "0" "-U" "backup" "-E" "-c" "archive 1;recurse;du" And it's working. Notably the command it says its running doesn't work by hand so I suspect that it's a different command being implemented. Now I'm getting more confused. I think I might point AMANDA at my remote samba server and do a packet trace to work out EXACTLY what it is sending over... that is essentially what amanda is doing in the two different cases you've tried (plus a few more smbclient arguments that shouldn't affect the behaviour you're experiencing). if those commands do not work as expected, then solve the samba problem and amanda should work as expected. Then explain the above. a note about this should probably be written in the docs/SAMBA file because 99% of the problems people have with amanda/samba backups are samba problems that should be debugged independently of amanda. Oh, I downloaded the patched version (as opposed to patching it myself) and it displays the same behaviour... DSL -- And though you turn from me To glance behind The Phantom of the Opera is there... Inside your mind!
Re: help me, more output from amcheck
Andrew! Amanda Tape Server Host Check - /holdingtank: 8182314 KB disk space available, that's plenty. NOTE: skipping tape-writable test. Tape nwc0 label ok. Server check took 17.913 seconds. "disklist", line 15: disk dumptype expected "disklist", line 16: disk dumptype expected amcheck-clients: could not load "disklist" What's up with the two disklist lines, line 15 16? Well, it's expecting a dumptype. I'm not entirely certain how to say that in a different way. However, the disklist looks like: [lloy0076 ]% cat disklist host.your.domain dump-type The dump-type is found in amanda.conf. Typical names are "comp-user". If you specify a wrong dumptype or no dumptype then you'll get this kind of error. Also, I've not specified any clients as yet in my amanda.conf, why is that last line even there? Well, because it couldn't figure out the disklist. It's related to the first problem, much like the domino effect - one problem causing another problem. DSL -- And though you turn from me To glance behind The Phantom of the Opera is there... Inside your mind!
HP - Pure Store DLT1 [new tape type]
I've just produced this for an HP-Pure Store DLT1 drive. It looks about
right (the drives claim 40Gb). This was created with mt -f /dev/nst1
datcompression off and with the tapetype that comes with amanda-2.4.2p1.
define tapetype HP-DLT1E {
comment "just produced by tapetype program"
length 38751 mbytes
filemark 0 kbytes
speed 2756 kps
}
DSL
--
And though you turn from me
To glance behind
The Phantom of the Opera is there...
Inside your mind!
Re: help me, more output from amcheck
Oops! However the syntax David Lloyd gave was not quite right. It should be: host.your.domain disk-to-back-up dump-type Damned Samba backups in disklists and god knows what... :-( -- And though you turn from me To glance behind The Phantom of the Opera is there... Inside your mind!
Samba Report
Hmmm! I have amanda-2.4.2p1 (I recently patched it), and despite the documentation saying /etc/amandapass should look like: [/etc]% cat amandapass //NAME/SHARE user%password It only works if I use [/etc]% cat amandapass //NAME/SHARE password I receive "host down or invalid password" errors otherwise. In addition, using ethereal (i.e. packet sniffer) I can see the DOS replies from the SMB server when using the first form. Now, I'm confused (although I have a working SAMBA backup system now). DSL -- And though you turn from me To glance behind The Phantom of the Opera is there... Inside your mind!
Samba Backups
Hmmm! I have compiled Samba 2.4.2 with: ./configure --with-libsmbclient (and the other options are the same as the ones that worked before) Added: [adlcds1 ]# cat /etc/amandapass //WEBAPP/Web asifiwouldtellapubliclist Added: [adlcds1 ]# cat disklist adlcds1 //WEBAPP/Web comp-tar BUT amcheck -c says it can't find the disk "//WEBAPP/Web"... And I don't know what's wrong...using smbclient by itself works correctly. DSL -- And though you turn from me To glance behind The Phantom of the Opera is there... Inside your mind!
Re: amlabel
H i 'm a Amanda Newbie using amanda-2.4.2, executing: su amanda amlabel -f amanda.conf DailySet1-000 getting the error message: amlabel: amlabel: cannot execute binary file I don't know what i did wrong... It might be worth BECOMING the amanda user and doing it. I always find "su user (some command)" tends to get things confused... DSL -- The Question Is: "Can AUUG augment LinuxSA?" (maybe it would be easier to ask Cornelia "who is the weakest link?")
Re: amrestore problem
Hi There! root@fileserver:/usr/local/sbin ./amrecover Daily AMRECOVER Version 2.4.2-19991216-beta1. Contacting server on fileserver ... 220 fileserver AMANDA index server (2.4.2-19991216-beta1) ready. 200 Access OK Setting restore date to today (2001-03-12) 200 Working date set to 2001-03-12. 200 Config set to Daily. 200 Dump host set to fileserver. Can't determine disk and mount point from $CWD amrecover What is wrong? In short NOTHING. When you start amrecover it assumes that you want to recover directly into your current working directory. You need to sethost, then setdisk. So, if I wanted to recover /usr on rebel.net.au I would do something like: amrecover sethost rebel.net.au [some response] amrecover setdisk /usr And continue... DSL -- Domine O venite O sacramentum eo deo Domine O venite O sacramentum eo deo Omnem crede diem tibi diluxisse supremum. Sacramentum eo deo
Re: hostname lookup failed
Charlie! Amanda Backup Client Hosts Check ERROR: office: [addr 192.168.0.83: hostname lookup failed] Client check: 1 host checked in 0.109 seconds, 1 problem found (brought to you by Amanda 2.4.2) But 'office' is really pingable in fact, What does: * nslookup 192.168.0.83 say? If that doesn't work, try dig 83.0.168.192.in-addr.arpa AMANDA needs to be able to reverse resolve the IP address to the correct hostname. DSL -- CWA - Chin Waggers Association "Let's sit around and complain about something. Our topic for today is: ADSL...h...that `L' stands for Linux doesn't it?"
Re: hostname lookup failed
Hmmm.. To disable it completely, I think you'd need to hack the source. DSL
Re: hostname lookup failed
Oops! To disable it completely, I think you'd need to hack the source. Obvously you don't need to but I wouldn't if I were you :-) DSL -- CWA - Chin Waggers Association "Let's sit around and complain about something. Our topic for today is: ADSL...h...that `L' stands for Linux doesn't it?"
Re: help
Ramesh! "/usr/local/etc/amanda/confname/amanda.conf",line 0:default tapetype EXABYTE not defined amcheck: could not find config file "/usr/local/etc/amanda/confname/amanda.conf" It can't find your configuration. Drop the -m switch - all that seems to do is make amcheck go quiet. Depending on how robust amcheck's argument parsing is, it could confuse it. Furthermore, you should setup a configuration directory with the same name as your configuration in /usr/local/etc/amanda/. My configuration is called NCI. Therefore I have: /usr/local/etc/amanda/NCI/amanda.conf We have got a Tandberg DLT-8000 40/80gb drive.In amanda.conf file I made an entry for this drive.But still it is refering the default tape drive. You still need to specify the tape device. See the example amanda.conf file for a detailed explanation of this. DL -- Domine O venite O sacramentum eo deo Domine O venite O sacramentum eo deo Omnem crede diem tibi diluxisse supremum. Sacramentum eo deo
Re: forcing level 0 backups
amadmin MYCONFIG force [share name] You could use a script to walk through you dump file thingo to do this... DL -- Domine O venite O sacramentum eo deo Domine O venite O sacramentum eo deo Omnem crede diem tibi diluxisse supremum. Sacramentum eo deo
Re: amanda mailing list
The alternative is to do what my local LUG does would be to add: * X-Mailing-List: [EMAIL PROTECTED] archive/latest/4749 (naturally amand-users wouldn't claim to be linuxsa :-P) And filter on that...every now and then someone will send you something directly and it will end up in the wrong box if you only filter on sender. However, if that header is kept your filtering doesn't break regardless of where the mail is sent from. DL
Re: test config creates problems perhaps
U... For me the ideal would be a test-mode where I could rerun repeatedly with the same tape, remove the switch and then it would be production, though I realize this may not be feasable with the amanda design philosophy. Still there must be a standard way to test. How do I create a test amanda.config that won't impact, any files used by the production amand.config? If the exclude list is confusing you - and that's all - why don't you test using tar MANUALLY (man tar - I think it's the -e option and also you can specify a file if you ferret about the man pages) and then transfer it to production and see what happens? DL -- Compromise or death, he fought 'til his last breath he never had it in him to surrender Just like me he never could surrender!
Re: Problem with amcheck
Ummm... The DNS is set up correctly. I have set up the primary DNS. It is working fine a lot of time. Is it working fine ALL the time or does it fail sometimes? DL -- You have a deformed comb, so go suck eggs...
Re: Help replacing tapes
Yikes! You can actually relabel the tape just after you have amrmtaped it. For AMANDA, after "amrmtape" the tape is "new", even if for you it is "old" ;-) I refuse to immediately reuse a tape after it's been amrmtaped because one of my other fellow system administrators amrmtaped a real tape forcibly and caused me to have a minor panic because for at least 5 days it was a case of "if the system goes down, it's a manual, down to your bones, dd/tar/restore job" :-( I say, even if you do amrmtape a tape, leave it alone for at least one day before you reuse it. At least then you have time to realise you shouldn't have...call me paranoid, but when data is money... DL -- You have a deformed comb, so go suck eggs...
Re: Amrecover issue
John et al: /usr/local/amanda/sbin/amrecover -s amandaserver.mydomain.com Are you certain the default configuration built into amrecover is the config you wanted to use? Put a different way, try this: I gave up using the "default" configuration because it would always "default" to something that didn't exist and wouldn't change. And some of the utilities pick it up and some of them don't. Furthermore, I don't like to use it because in an emergency backup situation where you manage to get AMANDA back onto the system, if you're used to typing "amdump MYCONFIG" or wotever then you've got one less headache in the heat of battle... DL -- The hate stands ready... Send forth your terror into HELL!
Re: amflush not deleting dumps
Hi! I've never had to post a question until now because I have always been able to find the answer by searching past emails - here's to a great program and it's great users! So this is my maiden voyage. I just upgraded to 2.4.2 and everything works fine, except that amflush doesn't delete the dump from the holding disk after it flushes from tape. Any ideas? It normally does. Have you checked what files are actually in your dump directory, their ownership and permissions? I had this problem and it turned out that our (archaic) password synchronisation system would surreptitiously change UID's and cause all types of problems. Also, does the report amflush makes say anything unusual? DL ps. I think your Outlook is producing HTML e-mails... -- Mortis et vitae rota Semper aqueae volvitur!
Re: hostnames do not match
Bernhard! And verify DNS reverse lookup Off the top of my head that gives a different error... :-) -- GOD SAVE AMERICA! - because President Bush, the Second Will Not!
Re: AMDUMP errors
Justin! The first one started to occur after rebuilding my Tape Backup Server after a Hard Disk Crash. I changed it from a SCSI disk to a IDE disk. Now when ever it goes to dump any of the file systems on that system (sol), it gives this in the AMDUMP report: solhda1 lev 0 FAILED [disk hda1 offline on sol?] Have you looked in /tmp/amanda/*.debug? Every now and then things will show up there. Do this on the backup and the client machine. ERROR: sol: [can not access hda1 (hda1): No such file or directory] Shouldn't it be /dev/hda1? And this is how it is configured in disklist: sol hda1 comp-root-tar The second error I am not to sure about: tigereye hda4 lev 0 FAILED [can't switch to incremental dump] There is no lock file. A default configuration will have the reserve parameter set to 100 per cent. When a dump fails, AMANDA will dump it to disk UNLESS the holding disk has less free space than that specified in the reserve parameter. If this is the case, it will bump the dump at least one level. In AMANDA parlance this is called "degraded dumps" (I think). You could set the reserve parameter to something lower. I have a large holding disk on my setup where I can actually stack 5 full days' backups into 85% of the disk space, so I only reserve 25%. Look in [amanda source directory]/examples/amanda.conf.in for another explanation of reserve. DL -- GOD SAVE AMERICA! - because President Bush, the Second Will Not!
Re: AMDUMP errors
Hmm... couple of choices to fix this: You could just let it ride, knowing that that disk isn't getting backed up, and sometime in the next few tapes, AMANDA might have enough space (because other disks backups get bumped to higher incremental levels) to do the level 0 backup; OR, you could temporarily edit That's dubious to say the least. If I'd taken this view last time I came up with a backup error, we would have lost another 2 days' worth of data which, in the words of our office manager, would have been absolute hell. I'd be inclined to manually afio or tar the whole disk onto tape until I sorted the AMANDA problem out... DL -- GOD SAVE AMERICA! - because President Bush, the Second Will Not!
Re: format of amandahosts file
Hmm! Of course, a DNS server would "simplify" things. But besides the theoretical point of "Occam's razor" (what is simple?), we have all these security announcements for bind, that make the blood chill, even with the most nuclearly hardened packet filter... Without being too laconic, your e-mail complaining about BIND probably took more characters than a simple BIND configuration...and if you're *really* worried about security why not try BIND 9 and turn on ipsec and DNSSEC and such... DL -- The new century begins at the end of this month; let the celebrations be brought forth let the people rejoice God Bless the Queen!
Re: Reading a file on the holding disk
Chris! Why does if=some device work and if=some file does not? Is this because I have an ext2 filesystem on the disk and copied the file with cp? If it's a file on an ext2 system, just use tar directly: tar -xzvf the_file OR tar --extract --gzip --verbose --file=the_file DL -- The new century begins at the end of this month; let the celebrations be brought forth let the people rejoice God Bless the Queen!
Re: no daily AMANDA MAIL REPORT was produced after successful run ofamdump
Denise! I forced a level 0 to run this afternoon - when it was done no AMANDA MAIL REPORT was generated. When I looked at the current info via amadmin I noticed that all of my partions were backed up to tape except sda10 which was 'forced to a level 0 dump on next run'. Was it, or was it not backed up? The info below suggests that it was... Current info for admin1.corp.walid.com sda10: (Forcing to level 0 dump on next run) Stats: dump rates (kps), Full: 3106.0, 3364.0, 3100.0 Incremental: 1735.0, 3089.0, 2364.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 20001203 daily1199 9341985 9341984 3007 Do you know why this happened and if I can re-generate the daily AMANDA MAIL REPORT? Look in the place that AMANDA logs. You'll see lots of amflush.# and amdump.#. Most people also keep their curinfo databases there as well. Ours is /usr/adm/amanda/[configuration name]/ In there run: [amanda@localhost MYCONFIG]% amstatus --file amdump.1 (.1 should be the latest set of dumps). You may want to pipe it to mail or use the operator to save it to file...although this isn't the full information it is a start. DL -- The new century begins at the end of this month; let the celebrations be brought forth let the people rejoice God Bless the Queen!
Re: amrecover
Brian and Alexandre! but once the process is finished, i get back the the amrecover prompt, and i cannot find the stuff i wanted to be restored. Note that stuff will be restored into a directory tree that mirrors the tree of the backed up filesystem. So, if you restore bar/baz that was originally in /foo, where /foo is the root of a filesystem (or a subdirectory of / listed in the disklist), amrecover will get you `bar/baz, not just `baz. The question is, does ANYTHING at all appear? Perhaps you could use another virtual terminal to do an `ls' after the recover returns a promptyou could use amrestore /dev/st0 hostname diskname and see what that turns up. Naturally you'd substitute the values I put in... DL -- Don't you find it rather touching to behold The OS that came in from the cold Seen for what it is: religion, plus finesse Countries, creeds, mean nothing - only Linux...
Re: Making backup to HDD only
You can kind of do it. Basically: Set the reserve parameter very low: reserve 0 And set the tape device to /dev/haha (unless you actually have a device called "/dev/haha"). You'll need to clear the backups manually when you want to get rid of them though...given that AMANDA names the directories with the dates, this shouldn't be too hard to do in PERL (or some other language with regular expressions). DL
Re: 2.4.2-RedHat7.0_runtar not executable
Tom! I've done about every alteration of the permissions of /usr/lib/amanda/runtar that I can think of and I still get the error below. Any direction would be appreciated! My guess is that it's a setuid program; I find these particular styles of programs difficult to get the permissions to stay correct. Generally: [root]# chown root.disk runtar [root]# chmod ug+rxs runtar What generally happens is that the chown dumps the sticky bit which causes the program to fail. One other thing you could try is to run AMANDA as root itself and see whether you still get the same error - if root itself can't actually run the program then it's obviously not a permission problem but something else. DL -- Don't you find it rather touching to behold The OS that came in from the cold Seen for what it is: religion, plus finesse Countries, creeds, mean nothing - only Linux...
Re: 2.4.2-RedHat7.0_runtar not executable
Tom! I remember for awhile, there were problems with some versions of tar and amanda. Is that still the case and if it is what versions are known to be compatible with 2.4.2 and what versions are not. I am using the binary tar-1.13.17-8 (i386.rpm) We're using 1.13.17-3 and it works fine here. I've just had another look at runtar and it is a setuid program. [amanda@adlcds1 libexec]$ ls -l runtar -rwsr-x---1 root amanda 77587 Oct 5 13:54 runtar The permissions must look something like that - if they don't it won't run. When I installed 2.4.2 amdump, this and almost everything that was setuid wouldn't work and it took me quite a bit of fiddling with permissions to convince the sticky bit to stick :-P DL -- Don't you find it rather touching to behold The OS that came in from the cold Seen for what it is: religion, plus finesse Countries, creeds, mean nothing - only Linux...
Re: GNU tar estimates for vfat filesystems (Was: How do I check level 1 sizes?)
Chris! My suspicion is that GNU tar, which I use in the version 1.12, somehow cannot compute incrementals right, for filesystems of vfat type that are mounted the way I described above...(?) Eeck! Even RedHat have a later version of GNU tar than 1.1.2 and (honestly) they're not known to release the latest versions of programs. Upgrade tar to at least (GNU tar) 1.13.17; the ones below this are likely to cause all sorts of weird problems. DL -- Don't you find it rather touching to behold The OS that came in from the cold Seen for what it is: religion, plus finesse Countries, creeds, mean nothing - only Linux...
Re: Why isn't amanda using my exclude list?
Paul! Any idea why amanda seems to be disregarding my exclude.gtar file? I found adding a "*" before a directory name totally stuffed things up. I have things like: ./squid Which gets rid of /home/squid and such... DL -- Don't you find it rather touching to behold The OS that came in from the cold Seen for what it is: religion, plus finesse Countries, creeds, mean nothing - only Linux...
amrmtape mistake
Someone I work with accidentally amrmtaped the wrong tape (number 10), but immediately flushed what was in the holding disk to the correct tape (number 15). Therefore I have the following situation: * I have all of tape 10's data (but it may or may not have a header) * I have the curinfo records that amrmtape saved Now, how would I get this tape back into operation? Or is there no way... DL -- Video killed the radio star! Video killed the radio star! In my mind and in my car - we can't rewind We've gone too far
Weird Block Size, Tapertype, Something Error
Hi There! Excuse my odd subject but I can't quite decide what has caused my whole AMANDA configuration to crash. On the weekend I built, installed and ran the tapetype program on my system. Unfortunately I had to change tape drives before I did this but it was exactly the SAME model (Seagate STT2-RCVT a Travan drive) as was taken out. Anyway, the person I work with adjusted the tapetype and the first odd thing that occured was: * st0: incorrect block size We amrmtaped the tape and relabeled it again. The dumps appeared to go the tape correctly. However, the next morning (we did another dump but this time to holding disk) the amflush reported an incorrect block size. I went in and investigated and discovered the following things: * amanda was wholly unable to read any of the "pre change block size/tape device" tapes - amverify would complain about the block size - forcing the block size to 0 caused amverify to read but it came up with things like "short header 412 bytes" - amrestore would complain that there was an EOF and that it had reached end of tape when the tapes, even when rewinding, take at least 5 minutes to go from one end to another and the tape I was restoring was very full * tar could read and write to tape - tar could read and write to the tape nicely I thought "this is a tapetype" mismatch. So I reset the tapetype back to the above and got the same errors. This of course implies one of our backup systems (we run two for safety purposes) is simply a) failing or b) almost impossible to restore. We have tried forcing compression on and off with still the same results. Any ideas what might cause this? DL -- Video killed the radio star! Video killed the radio star! In my mind and in my car - we can't rewind We've gone too far
Re: your mail
Joi et al: (I'm not positive about the read-write, but it definately needs read.) It appears that AMANDA must write to: * its config directories * /etc/dumpdates (if you're using dump) * /etc/amandates * /usr/adm/amanda or wherever you've set the log directories to * /tmp If it can't write to any of them it can simply die silently. No error. Nothing - especially if /tmp fails. amrecover and the index server seem to be the most susceptible to non-writable directories, although amandad and almost anything else that logs to /tmp can fail silently. I'm inclined to hack the source and stop it from dying without a trace; maybe a syslog of messages.critical saying there is no AMANDA logs would be better than being stuck without a backup! I must confess - although I've found AMANDA an excellent backup system and I've restored from it a number of times - I find that its error reporting is absolutely woeful and/or non-existent. DL -- Do you believe in life after love? I can feel something inside me, say I really don't think you're strong enough
Re: removing Warning Message from Amanda Report..
Ummm, what happens when you get a REAL error? DL
Re: Writeable conf directory?
Daniel! Does the AMANDA conf directory need to be writable? No, provided you set tapelist, disklist etc to some other, writable directory. read-write if it really needs it. Amcheck reports conf directory not writable. I'm thinking of commenting the conf directory check out of amcheck. Would that be a bad idea? Personally I don't think it's a problem; just note it in your documentation etc... DL -- Do you believe in life after love? I can feel something inside me, say I really don't think you're strong enough
Re: Not Getting Estimates
I forgot to say that I'm running: * RedHat Linux 6.2 - vanialla except for important updates * Latest Stable Release of dump for Linux - I got an RPM from sourceforge... dsl -- Do you believe in life after love? I can feel something inside me, say I really don't think you're strong enough
Re: one large partition
Hmm! I thought AMANDA only backed up whole "disks" or "partitions"...i.e: [lloy0076] % df /dev/hda /usr /dev/hdb /tmp And I would only be able to backup ALL hda or ALL hdb, but not just /usr/bin without getting into GNUTAR exclusions and such...maybe I'm wrong... DL
Re: Not Getting Estimates
John! What does amcheck have to say? Everything is OK (except I don't have any spare tapes for it to do a tape write test, but I've fixed that problem at last). What's in /tmp/amanda/sendsize*debug on adlcds1.nci.com.au? I'm not certain, but I'll have a look asap :-) DL -- Do you believe in life after love? I can feel something inside me, say I really don't think you're strong enough
Re: Help with FAILED AND STRANGE DUMP
The seek errors you're seeing generally occur because some other process is atempting to use the blocks that AMANDA (rather dump) is attempting to back up. I've noticed that if I get enough of them it just trashes my backup and I have to do it again :-) DL -- Do you believe in life after love? I can feel something inside me, say I really don't think you're strong enough
Re: Why isn't 2.4.2 out yet?
George! I'm still using 2.4.1p1. Can anyone give me good reason(s) to upgrade to 2.4.2? What do you gain by going to the new version, if anything? From what I understand the code for 2.4.2 is stable. It does have some more sane error messages, although to be honest I've not found any of AMANDA's error messages awfully direct... DL -- There's no time for us There's no place for us What is this thing that takes our dreams Yet gets away from us?
