RE: Tape drive device files
Have you verified that your kernel has loaded the appropriate module for the hardware, so that the system can interact with the device? Try here for linux documentation: http://tldp.org > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of LaValley, Brian E > Sent: Tuesday, August 09, 2005 10:52 AM > To: Amanda (E-mail) > Subject: Tape drive device files > > Can someone point me to a good educational site for /dev > information? I have attached a tape drive to my machine, but > I can't find the special files. I know it should be nst* but > they don't exist. Do they have to be created manually? > >
RE: Runtar error
Thank you to everyone that assisted me with this problem. In the end, removing the 'nosuid' from /etc/auto.net allowed autofs to mount the NFS shares correctly. As a result, I'm able to successfully backup the additional linux clients. -Rob
RE: Runtar error
Excellent point, Eric. My local automounter was mounting my NFS shares with nosuid. I have removed that entry. I no longer see nosuid in my mount listings. Lesse if it works :) -Rob PS - I'm crossing my fingers! > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Eric Siegerman > Sent: Monday, February 21, 2005 2:54 PM > To: Amanda Mailing List > Subject: Re: Runtar error > > On Fri, Feb 18, 2005 at 09:10:30AM -0600, Dege, Robert C. wrote: > > runtar: error [must be setuid root] > > On Fri, Feb 18, 2005 at 10:49:46AM -0600, Dege, Robert C. wrote: > > -rwsr-x--- 1 root amanda 9947 Feb 16 10:43 runtar > > [plus evidence that this copy of runtar *is* the one being used] > > Hmm, that looks like runtar complaining, so it must have been > executed. That argues against the hypothesis that Amanda > can't run runtar at all because it's not in the "amanda" group. > > And runtar clearly is setuid root. > > I wonder if the file system is mounted "nosuid". You > could test it by copying the "id" program into the directory > where runtar lives, making it setuid root, and running it as > a nonroot user to see what it says. (MAKE SURE to nuke your > copy as soon as you're finished with it; "id" presumably > hasn't been audited for setuid-safety!) > > On a Solaris box, I get (I've edited out the list of secondary > groups): > % pwd > /home/erics/test > > % ls -ld id > // I took away its world-execute more for security paranoia > // than for the sake of strictly emulating runtar's perms > -rwsr-x--- 1 root erics 8044 Feb 21 14:39 id > > // The real "id" command just says I'm me -- ho hum > % /bin/id -a > uid=1000(erics) gid=1000(erics) groups=... > > // My setuid-root "id" command. Still says my uid is my own, > // but note the "euid=0(root)"; that's what we're looking > // for. (euid==0 && uid==) is the sign of a > // setuid-root executable. (Similarly with gid's for setgid, > // but that's not relevent here.) > % ./id -a > uid=1000(erics) gid=1000(erics) euid=0(root) groups=... > > // And just as a check, run it from a root shell; the "euid=" > // has gone away, since both euid and ruid are now both 0. > # ./id -a > uid=0(root) gid=1(other) groups=... > > -- > > | | /\ > |-_|/ > Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED] > | | / > The animal that coils in a circle is the serpent; that's why > so many cults and myths of the serpent exist, because it's > hard to represent the return of the sun by the coiling of a > hippopotamus. > - Umberto Eco, "Foucault's Pendulum" >
RE: Runtar error
> Humm I missed this in the first read, did you do an ldconfig > after the install of the libs? And what do you mean by > building new libs? > Theres more to amanda than just the libs... I built the entire amanda package... My apologies for the misunderstanding. I did an ldconfig, and will find out tomorrow if that resolved the problem or not. If ldconfig were the issue, then wouldn't I see a problem when doing an amcheck on the amanda server? > Note the 's' in the perms. When you installed amanda, what user were you? > If it came from rpms, fuss at the packager, then remove it and put in the tarball home built > version, lots, lots less trouble in the long run. Gene, the ls -l showed tar, not runtar. Here is what my runtar shows: -rwsr-x--x 1 root amanda 9947 Feb 16 10:43 /usr/local/dist/libexec/runtar I'll update this thread tomorrow, and let you know if the ldconfig helped at all. Thanks for the input. -Rob
RE: Runtar error
> I think it is complaining about runtar not being suid root > like it's supposed to be. After you build amanda as the > appropriate user, you need to do the 'make install' as root > to get the proper permissiona and suid bits set appropriately. > > Frank Frank, I think so to, but when I did, ls -l, it shows the correct permissions: [EMAIL PROTECTED] amanda]# ls -l /usr/local/dist/libexec/ total 288 -rwxr-xr-x 1 amanda amanda 25853 Feb 16 10:43 amandad -rwsr-x--- 1 root amanda 12417 Feb 16 10:43 amqde -rwsr-x--- 1 root amanda 18015 Feb 16 10:43 calcsize -rwsr-x--- 1 root amanda 11872 Feb 16 10:43 killpgrp -rwxr-xr-x 1 amanda amanda 4822 Feb 16 10:43 patch-system -rwxr-xr-x 1 root root 28452 Feb 16 10:38 rmt -rwsr-x--- 1 root amanda 8536 Feb 16 10:43 rundump -rwsr-x--- 1 root amanda 9947 Feb 16 10:43 runtar -rwxr-xr-x 1 amanda amanda 25846 Feb 16 10:43 selfcheck -rwxr-xr-x 1 amanda amanda 54168 Feb 16 10:43 sendbackup -rwxr-xr-x 1 amanda amanda 41942 Feb 16 10:43 sendsize -rw-r--r-- 1 root root 798 Feb 3 13:35 sudo_noexec.la -rwxr-xr-x 1 root root4799 Feb 3 13:35 sudo_noexec.so -rwxr-xr-x 1 amanda amanda 7634 Feb 16 10:43 versionsuffix Plus, the amandad shows it checking the same runtar prog: OK / OK /usr/local/dist/libexec/runtar executable OK /usr/local/dist/bin/tar executable OK /etc/amandates read/writable OK /usr/local/amanda/gnutar-lists/. read/writable OK /bin/gzip executable OK /dev/null read/writable OK /tmp/amanda has more than 64 KB available. -Rob
Runtar error
Last night, I had two systems fail on new amanda libs that I built. Upon investigation, I found this in the runtar debug logs in /tmp/amanda: # more /tmp/amanda/runtar.20050217191004.debug runtar: debug 1 pid 11435 ruid 7510 euid 7510: start at Thu Feb 17 19:10:04 2005 /usr/local/dist/bin/tar: version 2.4.4p4 runtar: error [must be setuid root] runtar: pid 11435 finish time Thu Feb 17 19:10:04 2005 Yet, an ls -l shows # ls -l /usr/local/dist/bin/tar -rwxr-xr-x 1 root root 322664 Feb 16 10:38 /usr/local/dist/bin/tar And # /usr/local/dist/bin/tar --version tar (GNU tar) 1.13.25 Copyright © 2001 Free Software Foundation, Inc. I'm can't figure out why runtar is complaining like this. Any ideas? -Rob
RE: Runtar: Permission denied
Good call. I changed the xinetd.d/amanda file: group = diskto group = amanda That resolved the problem. Now what disturbs me is why the other linux box was able to work with that incorrect xinetd.d/amanda file. Time to do some more investigating :) -Rob > Amanda not in the amanda group on that system? > > Or amanda's primary group is not "amanda" and you forgot > "groups = yes" > in xinet.d/amanda to enable the additional groups? > > > -- > Paul Bijnens, XplanationTel +32 > 16 397.511 > Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 > 16 397.512 > http://www.xplanation.com/ email: > [EMAIL PROTECTED] > ** > * > * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, > ^Q, F6, * > * quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, > bye, /bye, * > * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, > hangup, * > * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, > shutdown, * > * kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, > ...* > * ... "Are you sure?" ... YES ... Phew ... I'm out > * > ** > * > > >
Runtar: Permission denied
I'm adding a new linux client to my current amanda backup system. I built & installed the binaries, added the system to the disklist, and ran an amcheck -c. For some odd reason, I get a runtar permissions error, and I can't figure out why. I compared the build to other functioning systems, but cannot find the problem. Here is all the relevant info: OS: Fedora Core 3 w/ Kernel 2.6.10 Amanda: version 2.4.4p4 Segment from /tmp/amanda/amandad...debug: OK /var OK /var OK /var OK / OK / OK / ERROR [can not execute /usr/local/dist/libexec/runtar: Permission denied] OK /usr/local/dist/bin/tar executable OK /etc/amandates read/writable OK /usr/local/amanda/gnutar-lists/. read/writable OK /bin/gzip executable OK /dev/null read/writable OK /tmp/amanda has more than 64 KB available. OK /tmp/amanda has more than 64 KB available. Listing of /usr/local/dist/libexec: -rwxr-xr-x 1 amanda amanda 25853 Feb 16 10:43 amandad -rwsr-x--- 1 root amanda 12417 Feb 16 10:43 amqde -rwsr-x--- 1 root amanda 18015 Feb 16 10:43 calcsize -rwsr-x--- 1 root amanda 11872 Feb 16 10:43 killpgrp -rwxr-xr-x 1 amanda amanda 4822 Feb 16 10:43 patch-system -rwsr-x--- 1 root amanda 8536 Feb 16 10:43 rundump -rwsr-x--- 1 root amanda 9947 Feb 16 10:43 runtar -rwxr-xr-x 1 amanda amanda 25846 Feb 16 10:43 selfcheck -rwxr-xr-x 1 amanda amanda 54168 Feb 16 10:43 sendbackup -rwxr-xr-x 1 amanda amanda 41942 Feb 16 10:43 sendsize -rwxr-xr-x 1 amanda amanda 7634 Feb 16 10:43 versionsuffix Any suggestions or insight is appreciated. I'm sure this is something simple that I just can't see. -Rob
amandad error
I'm trying to get amandad running on a client. When I run 'amcheck -c', I get the following error message from syslog: Dec 22 16:21:34 alpha09 inetd[426248]: someone wants amanda fd 24 rad_id -1 Dec 22 16:21:34 alpha09 inetd[426268]: 426268 execl /usr/local/dist/libexec/amandad rad_id -1 Dec 22 16:21:34 alpha09 inetd[426248]: 426268 reaped rad_id -1 Dec 22 16:21:34 alpha09 inetd[426248]: /usr/local/dist/libexec/amandad: exit status (1) Dec 22 16:21:34 alpha09 inetd[426248]: restored amanda, fd 24 Does anyone have any idea what this means?? Network info Server: x86 linux box with amanda-2.4.4p3 Client: TRU64 5.1B alpha with amanda-2.4.4p4 -Rob
RE: 3-hole.ps template working
Where can I can the updated 3hole.ps file? Is it avail. in cvs? -Rob > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] > Sent: Monday, November 15, 2004 9:50 AM > To: [EMAIL PROTECTED] > Subject: Re: 3-hole.ps template working > > > On Mon, Nov 15, 2004 at 07:45:52AM -0600, Dege, Robert C. wrote: > > > > John, > > > > what problems were you experiencing with the template? > I've been having issues as well, and am wondering if your > fixes to the template will resolve the problems I've been > experiencing. > > > > Not my solution, but Eric Siegerman's with some initial > input from Gene Heskett and Michael Brantley. > > My problem was that if the tape had sufficient DLE's to need > a second page of the postscript report, it would hang several > different postscript interpreters. Yet, if I went into the > postscript output file and split the two pages into separate > files, each printed fine. > > > -- > Jon H. LaBadie [EMAIL PROTECTED] > JG Computing > 4455 Province Line Road(609) 252-0159 > Princeton, NJ 08540-4322 (609) 683-7220 (fax) >
RE: 3-hole.ps template working
John, what problems were you experiencing with the template? I've been having issues as well, and am wondering if your fixes to the template will resolve the problems I've been experiencing. -Rob > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] > Sent: Thursday, November 11, 2004 4:45 PM > To: Jon LaBadie > Subject: 3-hole.ps template working > > > For those who may have had problems with the > postscript template "3-hole", I can report my > problems with it have been solved with the > latest revision. Thanks to Eric Siegerman > and anyone I may have omitted. > > It got a good workout last evening, 160 DLEs > on 3 tapes. One tape, with 90+ DLEs, took two > pages to complete the report (flawlessly). > > -- > Jon H. LaBadie [EMAIL PROTECTED] > JG Computing > 4455 Province Line Road(609) 252-0159 > Princeton, NJ 08540-4322 (609) 683-7220 (fax) >
RE: Amanda refusing to reuse old tapes
I'm just thinking out loud here . In your amanda.conf, you show "tapecycle 35 tapes", but do you actually have 35 tapes labeled & listed in tapelist? I ran into this problem with amanda at one point. I had tapecycle 40, but only had 20 tapes labeled. As a result, amanda was looking for the 21st tape, instead of looping back to tape #1. Lowering the tapecycle to 20 fixed the problem. -Rob > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] > Sent: Tuesday, August 17, 2004 9:38 AM > To: [EMAIL PROTECTED] > Subject: Amanda refusing to reuse old tapes > > > Am I missing something really easy here > > I have 35 tapes in rotation with a Dell Powervault 120T 7 > tape autochanger. > > Usually the backups only take about 2 or 3 tapes, I have > runtapes set to 4 just in case. This is still a work in > progress. The problem that I am having is that when amanda > uses the the last set of tapes (DailyDLT-29-35) > and the next available tapes (DailyDLT-01-07) are loaded, > amanda thinks they are active and refuses to use them. For > example, even though the tape list shows an entry like > "20040801 DailyDLT-01 reuse " well over > the 7 day dumpcycle and not even containing data that is > needed for a full dump, amanda still thinks the tape is > active and won't use it. For a workaround i keep having to > amrmtape and amlabel to relabel it and set > tapelist right- I know I must be missing something simple... > Am I correct in understanding that by setting the dumpcycle > to one week that amanda should happily reuse any tape older > than seven days provided there > were not any errors in the previous weeks run? > > Here's an excerpt from my amanda.conf: > dumpcycle 7 days > runspercycle 7 > tapecycle 35 tapes > bumpsize 20 Mb > bumpdays 1 > bumpmult 4 > etimeout -3600 > dtimeout 1800 > ctimeout 1300 > tapebufs 20 > runtapes 4 > > Thanks for any help!! > > Jay > -- > __ > Check out the latest SMS services @ http://www.linuxmail.org > This allows you to send and receive SMS through your mailbox. > > > Powered by Outblaze >
RE: Printout Reports
> Please put in some line breaks. Each of your paragraphs > shows up as one > line to me. I totally blame Outlook for that! Actually, I blame my company for forcing me off of pine ;) > > 2) amanda will no longer print out reports after a > successful backup. > > The program used to, but we had to turn it off a long time ago (by > > commenting out the printer line in amanda.conf). If I manually lpr > > ./amanda.conf as user amanda, I get a printout. So I'm looking for > > anytime of debugging techniques, or suggestions so that I > can get this > > excellent feature working again :) > > Make sure you have a lbl-templ defined in your tapetype in > amanda.conf. This was my problem. During the off time, I upgraded the tape device, thus creating a new tapetype entry. As a result, I failed to transfer over the lbl-templ entry in the new tapetype. I do have a 3rd related question. I am now able to print an amanda report successfully. However, when I run amreport to print out a worklog, the printer uses 11x17 paper, instead of the standard 8.5x11. If I run a standard lpr command as amanda, it will use the standard 8.5x11 paper. Is there some way to fix (or force) amreport to use the standard 8.5 paper size by default? -Rob
Printout Reports
Hey all, I have (2) issues with printing reports that I'm hoping someone can assist me with. 1) Can I print old reports from previous backups (for cataloging purposes)? I think I can do that using amreport, but I want to verify this. If not, what do I have to do? 2) amanda will no longer print out reports after a successful backup. The program used to, but we had to turn it off a long time ago (by commenting out the printer line in amanda.conf). If I manually lpr ./amanda.conf as user amanda, I get a printout. So I'm looking for anytime of debugging techniques, or suggestions so that I can get this excellent feature working again :) -Rob
RE: please, help with samba/windows setup
A few things I would check: *) Since you area already part of a domain, your amandapass does not require the third field that specifies the workgroup. *) Your disklist specifies nocomp-user-gnutar as the backup method. What is listed in there? *) check out the errors logs in /tmp/amanda. It might help highlight a few issues with the backup errors. *) The packages that you are using are fairly old. You might want to try upgrading them as the updated package might contain fixes relevant to your problem. I am able to successfully backup windows2000 systems using amanda on a redhat box, so I do know that this works. It has nothing to do with your linux box needing to be a PDC. So long as your linux box is a member of the domain, you should be okay. -Rob > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] > Sent: Thursday, July 08, 2004 9:34 AM > To: [EMAIL PROTECTED] > Subject: please, help with samba/windows setup > > > Hi there ! > > I am having trouble to setup amanda to backup shares from a > Windows 2000 server. I am not sure this is possible, (I suspect is > not), so I am writing to get a confirmation that this is impossible > and ask for suggestions to backup the windows 2000 shares. > > The PDC is a windows 2000 machine. it's NetBIOS name is > kgbserver. The shares that I want to backup are named > "//kgbserver/Others" and "//kgbserver/Docs". > > The amanda server is a RH9.0, with samba configured as > security=DOMAIN . The samba NetBIOS name is KGBSERVER2. > > This is why I think this could be a problem. The samba > server is not the PDC for that domain. It is just a client for that > domain. This makes any sense ? > > In the disklist file I put the following lines for the > shares I want to backup: > > kgbserver2 //kgbserver/Others nocomp-user-gnutar > kgbserver2 //kgbserver/Docs nocomp-user-gnutar > > The file /etc/amandapass was configured with the > Administrator and password for the Windows machine: > > //kgbserver/Others administrator%ajjj882 KGB > //kgbserver/Docsadministrator%ajjj882 KGB > > > On the amanda server (RH9.0) I can browse the Windows 2000's > shares with smbclient, for example: > > # smbclient -L //kgbserver -U administrator%ajjj882 -W KGB > added interface ip=192.168.155.202 bcast=192.168.155.255 > nmask=255.255.255.0 > Domain=[KGB] OS=[Windows 5.0] Server=[Windows 2000 LAN Manager] > > Sharename Type Comment > - --- > > ...etc... and browsing a specific share: > > # smbclient //kgbserver/Others -U administrator%ajjj882 -W KGB > added interface ip=192.168.155.202 bcast=192.168.155.255 > nmask=255.255.255.0 > Domain=[KGB] OS=[Windows 5.0] Server=[Windows 2000 LAN Manager] > smb: \> ls > . D0 Fri Jun 25 > 14:46:26 2004 > .. D0 Fri Jun 25 > 14:46:26 2004 > ENVELOPES D0 Thu Feb 28 > 15:02:23 2002 > > ...etc > > ...and even smbtar work fine: > > # cd /tmp > # smbtar -s kgbserver -u administrator%ajjj882 -x Others -t > others.tar > # tar -tvf others.tar > ...etc... > > ...and amcheck works fine too: > > # /bin/su - amanda -c "/usr/sbin/amcheck -c DialySet1" > > Amanda Backup Client Hosts Check > > Client check: 2 hosts checked in 10.682 seconds, 0 problems found > > (brought to you by Amanda 2.4.3) > > > The amdump fail with the following message: > > FAILURE AND STRANGE DUMP SUMMARY: > planner: ERROR Request to kgbserver2 timed out. > > and from DUMP summary: > > DUMP SUMMARY: > DUMPER STATSTAPER > STATS > HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS > KB/s > -- - > > kgbserver2 -ver/Others MISSING > -- > kgbserver2 -erver/Docs MISSING > -- > > Is this setup really impossible ? > As last resort, I configured Amanda to backup the mount > point "/mnt/kgbserver/Others" and "/mnt/kgbserver/Docs" from the > machine kgbserver2. > > These mount points are mounted at boot time via /etc/fstab using > smbfs. > > Is there another better solution ? > > I will appreciated any ideas and comments. > > thank you gurus in advance, > > Amanda server: RH9.0, running 2.4.20-30.9. > amanda version: 2.4.3-4 (from the rpm package) > samba version: 2.2.7a release 8.9.0 (from the rpm package) > > -- > Miguel Angelo Rozsas > K3M Consultoria > 19 3232 8886 > > --- > Est
RE: Installation problems
Steve, try checking out the logs in /tmp/amanda (if that's where your logs are set to for the client). You can check rundump or sendsize. It should show you the absolute path of the dump program and possibly any parameters used when performing the dump command. -Rob > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] > Sent: Wednesday, July 07, 2004 5:16 PM > To: [EMAIL PROTECTED] > Subject: Installation problems > > > Hello, > > I've recently started trying to get amanda installed (the > newest version as of a week ago) on a few of my linux boxes > here in the shop and I've come across two problems. The the > server install went smoothly on my Debian Sarge install, as > well as a client install on 3 Fedora boxes. However, when I > did a client install on two of my other debian boxes, amcheck > returns that it cannot find DUMP on those machines. I've > checked all of the following: > 1) Dump is installed > 2) The amanda user has priveleges to use dump > 3) Permissions are exactly the same as on my my working > amanda server as well as the working fedora boxes. > > > I've checked the FAQ on the website as well as the help > documents included with amanda and these mainly suggest that > if dump works for the user on the client machine, it should > for the server. Soo..I'm stuck. > > If anyone has any ideas about what I should be checking > /doing I'd greatly appreciate it! > > Thanks! > -Steve > > >
RE: amcheck -m DailySet1
The '-m' parameter will only send you an email if there are errors during the amcheck. If you want to receive an email on any amcheck output, try using '-a' instead. # amcheck -a DailySet1 -Rob > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] > Sent: Wednesday, July 07, 2004 8:06 AM > To: [EMAIL PROTECTED] > Subject: amcheck -m DailySet1 > > > When I run amcheck -m DailySet1 i dont receive mails in my inbox > i have set mailto in the amanda.conf file to my emailid > [EMAIL PROTECTED] > > What could be the reason > > -- > > Regards, > > Kaushal Shriyan > > Technical Engineer > Red Hat India Pvt. Ltd. > Tel : +91-22-22881326/27 > Fax : +91-22-22881318 > Cell : +91-9820367783 > > >
RE: AIT-2
> gnutar jumped from 1.13.25 to 1.13.9? in one leap. > Some reported problems with these very recent versions. > I don't recall the nature of the problems, check the archives. > But a build of 1.13.25 would seem a reasonable approach to > see if that is the problem. I was originally having this problem with tar 1.13.25 && gzip 1.3.3. I upgraded both tools to see if it had any affect. When amanda compresses a backup image, does it use gzip or does it use the built in compression that is available in gtar (tar -z)? -Rob
RE: AIT-2
It's been over a month, and I'm still having problems with my AIT-2 tape drive (seems like I'm having a lot of amanda problems in general as of late). As a recap... I could successfully run amdump & have amanda write dumps to tape. But when I tried to restore data from Amanda via "am recover", I would get the following errors: tar: Skipping to next header tar: Archive contains obsolescent base-64 headers tar: A lone zero block at 1639303 tar: Error exit delayed from previous errors extract_list - child returned non-zero status: 2 I've made more progress & am able to center in on the problem, I just don't know how to resolve it. My problem occurs when I use compression on a backup, and have the backup written to tape. For example: Backup using Compression Fast with GNUTAR = *) Amrecover restoring data from an image in the holding disk - successful *) Amrecover restoring data from an image written to an AIT-2 tape - fails Backup using no Compression with GNUTAR === *) Amrecover restoring data from an image in the holding disk - successful *) Amrecover restoring data from an image written to an AIT-2 tape - successful My current Config: Amanda - 2.4.4.p1 Tar - 1.13.94 Gzip - 1.3.5 Any suggestions are appreciated. -Rob
RE: Multiple NICs
Thank you all for the prompt replies. I was hoping that this would be a simple task of telling amanda what interface to communicate on. But because I have 2 interfaces on the same subnet, this forces me to alter how the system itself routes data using the 2 interfaces. Right now, the system is currently in use by the company, so I can't start futzing with the networking on the machine. Instead, I'm going to keep this on the back-burner for a later time. -Rob > -Original Message- > From: Nicki Messerschmidt, Linksystem Muenchen GmbH > [mailto:[EMAIL PROTECTED] > Sent: Thursday, June 03, 2004 4:59 AM > To: Dege, Robert C. > Cc: [EMAIL PROTECTED] > Subject: Re: Multiple NICs > > > Dege, Robert C. said the following: > > Our amanda server has 2 NICs in it, each with separate IPs. We're > > running 2.4.22 kernel, RedHat 9, Amanda 2.4.4p1. > > We'd like to back up a particular machine over the second NIC > > exclusively; is there a way to do that? We want our 1 NIC to be > > dedicated for NFS, and the other NIC to be dedicated for Amanda > > traffic. > > Both NICs on the server are on the same subnet, and the IP of our > > client systems are on that subnet as well. > > Any hints, suggestions, or "point me at some docs" are appreciated. > > How about setting a host route via the one seperate > interface? Otherwise > there could be a possibility setting an extended route vi the > "ip route" > command (source routing). > > > Cheers > Nicki > > -- > Linksystem Muenchen GmbH [EMAIL PROTECTED] > Schloerstrasse 10 http://www.link-m.de > 80634 Muenchen Tel. 089 / 890 518-0 > We make the Net work. Fax 089 / 890 518-77 > PGP Keys: https://www.link-m.de/pgp/ >
Multiple NICs
Hello, Our amanda server has 2 NICs in it, each with separate IPs. We're running 2.4.22 kernel, RedHat 9, Amanda 2.4.4p1. We'd like to back up a particular machine over the second NIC exclusively; is there a way to do that? We want our 1 NIC to be dedicated for NFS, and the other NIC to be dedicated for Amanda traffic. Both NICs on the server are on the same subnet, and the IP of our client systems are on that subnet as well. Any hints, suggestions, or "point me at some docs" are appreciated. Thanks! -Rob
RE: MapBarCode error
The -genconf did identify my two tape drives, however, it only produced a single config. It also didn't generate any information for the amanda.conf file, only the chg-scsi.conf file. Here is the output: # ~/libexec/chg-scsi bash$ ./chg-scsi -genconf Count 1 Count 2 # Please replace every ??? with the correct parameter. It is not possible # to guess everything :-) # If the option is not needed, cleanmax for example if you have no cleaning # tape remove the line. # number_configs 1 # Number of configs, you can have more than 1 config # if you have for example more than one drive, or you # to split your lib to use different dump levels # emubarcode 1 # If you drive has no barcode reader this will try # keep an inventory of your tapes to find them faster # havebarcode 0 # Set this to 1 if you have an library with an installed # barcode reader # debuglevel 0:0 # For debuging, see the docs /docs/TAPE-CHANGER # eject??? # set this to 1 if your drive needs an eject before move # sleep??? # How long to wait after an eject command before moving # the tape # changerdev /dev/sg0 # This is the device to communicate with the robot # # Here now comes the config for the first tape config 0 # This value is the one which is used in the amanda # config file to tell the chg-scsi programm which tape # and which slots to use # cleancart??? # The slot where the cleaning tape is located # remove it if you have no cleaning tape # drivenum 0 # Which tape drive to use if there are more than one drive # dev ??? # Which is the raw device to read/write data from the tape # It is important to use the non rewinding tape, like # /dev/nrst0 on linux, /dev/nrsa0 on BSD # startuse 0 # Which is the first slot to use # enduse24 # Which is the last slot to use # decrement this value by 1 if you have an # cleaning tape in the last slot # statfile /mnt/raid/amanda/libexec/tape0-slot # cleanfile /mnt/raid/amanda/libexec/tape0-clean # usagecount /mnt/raid/amanda/libexec/tape0-totaltime # tapestatus /mnt/raid/amanda/libexec/tape0-tapestatus # labelfile /mnt/raid/amanda/libexec/labelfile # > -Original Message- > From: Gene Heskett [mailto:[EMAIL PROTECTED] > Sent: Tuesday, June 01, 2004 11:20 AM > To: [EMAIL PROTECTED] > Subject: Re: MapBarCode error > > > On Tuesday 01 June 2004 10:29, Dege, Robert C. wrote: > >Gene, > > > >you were absolutely right! > > :) You can bring your reply to my private message back to > the list as > others may benefit from your findings. > > >When I was configuring amanda, I ran > > > ># ./chg-scsi -genconf > > > >to generate the chg-scsi.conf file for my Tape Changer. By default, > > it included emubarcode & havebarcode. By commenting these options > > from the file, I no longer received those error messages. > > > >-Rob > > > >> -Original Message- > >> From: Gene Heskett [mailto:[EMAIL PROTECTED] > >> Sent: Friday, May 28, 2004 5:07 PM > >> To: [EMAIL PROTECTED] > >> Subject: Re: MapBarCode error > >> > >> On Friday 28 May 2004 15:31, Dege, Robert C. wrote: > >> >Hello all, > >> > > >> >when I try to run amcheck, I keep getting a MapBarCode error, > >> > which causes amcheck to exit tape scanning prematurely. Here's > >> > a snippet of output: > >> > > >> >bash$ amcheck simnet > >> >Amanda Tape Server Host Check > >> >- > >> >Holding disk /mnt/raid/holding: 3250292 KB disk space available, > >> > that's plenty amcheck-server: slot 3: date 20180417 label > >> > SIMNET-04 (active tape) amcheck-server: fatal slot MapBarCode,: > >> > DB Version does not match ERROR: new tape not found in rack > >> > (expecting a new tape) > >> >NOTE: skipping tape-writable test > >> >Server check took 141.154 seconds > >> > > >> >Amanda Backup Client Hosts Check > >> > > >> >Client check: 2 hosts checked in 0.121 seconds, 0 problems found > >>
RE: MapBarCode error
Gene, you were absolutely right! When I was configuring amanda, I ran # ./chg-scsi -genconf to generate the chg-scsi.conf file for my Tape Changer. By default, it included emubarcode & havebarcode. By commenting these options from the file, I no longer received those error messages. -Rob > -Original Message- > From: Gene Heskett [mailto:[EMAIL PROTECTED] > Sent: Friday, May 28, 2004 5:07 PM > To: [EMAIL PROTECTED] > Subject: Re: MapBarCode error > > > On Friday 28 May 2004 15:31, Dege, Robert C. wrote: > >Hello all, > > > >when I try to run amcheck, I keep getting a MapBarCode error, which > > causes amcheck to exit tape scanning prematurely. Here's a snippet > > of output: > > > >bash$ amcheck simnet > >Amanda Tape Server Host Check > >- > >Holding disk /mnt/raid/holding: 3250292 KB disk space available, > > that's plenty amcheck-server: slot 3: date 20180417 label SIMNET-04 > > (active tape) amcheck-server: fatal slot MapBarCode,: DB Version > > does not match ERROR: new tape not found in rack > > (expecting a new tape) > >NOTE: skipping tape-writable test > >Server check took 141.154 seconds > > > >Amanda Backup Client Hosts Check > > > >Client check: 2 hosts checked in 0.121 seconds, 0 problems found > > > > > >Does anyone know why I'm getting this error message? I'm using > > amanda with a Qualstar TLS-4222 with (2) SDX-700C AIT3 tape drives. > > There is no BarCode reader in the unit. > > > >-Rob > > It sounds as if you may have either emubarcode, or something similar > in your amanda.conf. There are a couple of keywords in amanda that > (I've surveyed the code in question) if found, default to yes, so the > only way to shut things up is to comment those lines out. I believe > thats one of them. > > -- > Cheers, Gene > "There are four boxes to be used in defense of liberty: > soap, ballot, jury, and ammo. Please use in that order." > -Ed Howdershelt (Author) > 99.23% setiathome rank, not too shabby for a WV hillbilly > Yahoo.com attorneys please note, additions to this message > by Gene Heskett are: > Copyright 2004 by Maurice Eugene Heskett, all rights reserved. >
MapBarCode error
Hello all, when I try to run amcheck, I keep getting a MapBarCode error, which causes amcheck to exit tape scanning prematurely. Here's a snippet of output: bash$ amcheck simnet Amanda Tape Server Host Check - Holding disk /mnt/raid/holding: 3250292 KB disk space available, that's plenty amcheck-server: slot 3: date 20180417 label SIMNET-04 (active tape) amcheck-server: fatal slot MapBarCode,: DB Version does not match ERROR: new tape not found in rack (expecting a new tape) NOTE: skipping tape-writable test Server check took 141.154 seconds Amanda Backup Client Hosts Check Client check: 2 hosts checked in 0.121 seconds, 0 problems found Does anyone know why I'm getting this error message? I'm using amanda with a Qualstar TLS-4222 with (2) SDX-700C AIT3 tape drives. There is no BarCode reader in the unit. -Rob
RE: Error compiling on TRU64 4.0F
I figured out the problem. snprintf & vsnprintf are absent in libc for TRU64 4.0F. However, they can be found in the libdb.so library. So, I was able to fix my problem by adding LD="-ldb" to the configure line. -Rob > -Original Message----- > From: Dege, Robert C. > Sent: Friday, May 28, 2004 9:47 AM > To: Amanda List (E-mail) > Subject: Error compiling on TRU64 4.0F > > > > Hi, > > I'm trying to build amanda client binaries for TRU64 4.0F. I > am able to run configure fine (minus /sbin/dump issues). > When I run make, it errors out with the following message: > > cc -g -o .libs/amqde amqde.o ./.libs/libamclient.so > ../common-src/.libs/libamanda.so -lm -ltermcap -rpath > /mnt/raid/dist/lib > ld: > Unresolved: > snprintf > *** Exit 1 > Stop. > *** Exit 1 > > Anybody understand why this is failing? > > -Rob > > PS - here is my configure line: > > ./configure --prefix=/mnt/raid/dist --with-suffixes=no > --with-index-server=main --with-user=amanda > --with-group=amanda --without-server --without-restore > --without-amrecover --with-config=simnet > --with-gnutar=/mnt/raid/dist/bin/tar --with-smbclient=no >
Error compiling on TRU64 4.0F
Hi, I'm trying to build amanda client binaries for TRU64 4.0F. I am able to run configure fine (minus /sbin/dump issues). When I run make, it errors out with the following message: cc -g -o .libs/amqde amqde.o ./.libs/libamclient.so ../common-src/.libs/libamanda.so -lm -ltermcap -rpath /mnt/raid/dist/lib ld: Unresolved: snprintf *** Exit 1 Stop. *** Exit 1 Anybody understand why this is failing? -Rob PS - here is my configure line: ./configure --prefix=/mnt/raid/dist --with-suffixes=no --with-index-server=main --with-user=amanda --with-group=amanda --without-server --without-restore --without-amrecover --with-config=simnet --with-gnutar=/mnt/raid/dist/bin/tar --with-smbclient=no
dd question
Every so often, I'll run the following command to quickly see which amanda tape is currently in my tape drive: # dd if=/dev/nst0 bs=32k Most of the time, I'll get the header information, but every so often I have to run the command twice for the system to successfully read the tape. i.e.: bash$ dd if=/dev/tape bs=32k 0+0 records in 0+0 records out bash$ dd if=/dev/tape bs=32k AMANDA: TAPESTART DATE 20180319 TAPE SIMNET-02 1+0 records in 1+0 records out Any idea why this happens? -Rob
RE: AIT-2
First, thanks to all for your suggestions. I've gotten slighty farther with fixing this problem with my AIT-2 Tape Drive. After a few changes, I am able to restore a lot more files before amrestore crashes. Here's what I did: 1) Power off tape changer & system 2) Change dip switches on the AIT-2 tape drive so that 7-off & 8-on. This essentially turns off hardware commpression & turns on software compression 3) reboot the system. Before I try anymore tests, I'm going to re-run amtapetype again, and then run a few backups withthe new config. -Rob
RE: AIT-2
Jay, thanks for all this info. I am able to run these dd commands successfully. So I'm beginning to think that amanda is the source of the problem. However, before I go any further, I'm extracting the data from the tapeimages to ensure that tar doesn't crash. -Rob > -Original Message- > From: Jay Fenlason [mailto:[EMAIL PROTECTED] > Sent: Wednesday, April 07, 2004 5:20 PM > To: Dege, Robert C. > Subject: Re: AIT-2 > > > On Wed, Apr 07, 2004 at 01:23:53PM -0700, Dege, Robert C. wrote: > > > > > > > Can you take one of your backup tapes and access the files on it > > > reliably with dd? If you can't, it's likely to be a > hardware/os/etc > > > problem. If you can, it may be an Amanda problem. > > > > > > Is there any chane of bad termination on your SCSI chain? > > > > What would the dd command line be? > > Start with the tape rewound. > cd to a directory with a lot of space. (Up to 50Gb if you want to > read your entire AIT-2 tape.) > > dd < /dev/nst0 > tapeimage.1 bs=32k > dd < /dev/nst0 > tapeimage.2 bs=32k > dd < /dev/nst0 > tapeimage.3 bs=32k > dd < /dev/nst0 > tapeimage.4 bs=32k > dd < /dev/nst0 > tapeimage.5 bs=32k > dd < /dev/nst0 > tapeimage.6 bs=32k > ... > (Repeat the dd command until it creates an empty file.) > > The first tapeimage file will be the Amanda tape label. The last file > with data in it will be the Amanda tape end marker. The other files > will be the backups. If dd read all the backups and the end marker > successfully, any remaining problem is likely to be Amanda's. > > Each of the backups is going to be a (possibly compressed) dump output > file or a (possibly compressed) tar file. Either way, there's a 32k > header that you need to skip over to get at the actual data. If > they're tar files, you should be able to read them with > > dd < tapeimage.n bs=32k skip=1 | gtar tvf - > > If they're compressed tar files, you'll need > > dd < tapeimage.n bs=32k skip=1 | gunzip | gtar tvf - > > If they're dump files, I don't know how to read them. Check the > restore man page. > > > Right now, I'm running a tar command directly to a standard AIT-2 > > tape. I want to see if the problem is with tar, or with > amanda using > > tar. I'm tarring files to the tape, and then will try to > extract the > > files. I'm also using the same file chunk that failed on amanda to > > eliminate any additional variables in my test. > > > I don't think SCSI termination is the problem since I can use the > > tape changer without any problems, and backups occur > without error on > > a nightly basis. I'll double-check tough. > > If it's a hardware or OS problem, your tar test should find it. > > -- JF >
RE: AIT-2
> Are you recovering on the client or the server? > Are you recovering from more than one DLE? > Perhaps the data was compressed on a box using a compression program > not available on the box doing the recover. > > Frank The system is both the client & the server. I checked the config file in the source code, and verified that amanda is using /bin/gzip, and /bin/gtar. Right now, I'm only trying to restore from a single DLE. One thing that I did notice is that I built amanda using additional CFLAGS. Do you these extra optimizations might be causing the problem? (This is one of those out field kind of questions) -Rob
RE: AIT-2
> what platform/OS is your tapehost? AMD System, running RedHat 9.0. I'm using a stock 2.4.22 kernel. > did you also modify your SCSI tape driver config file > (/kernel/drv/st.conf > on Solaris) so the driver can know about particular capabilities of > the tapedrive? I didn't modify any kernel source files. I'm using 2 modules, st.o for the tape drive, and sg.o for the tape changer. > only with larger tape files, e.g. over ~16Gb in size. symptom was > device timeouts on the tape device, and amanda "thought" these dumps > were successful! Really? How were you able to resolve this problem? Did you lower chunksize or something similar in the amanda.conf file? -Rob
RE: AIT-2
> On my SDX-500 AIT-2 drives, I have 1-7 off and 8 on. The > documentation > says switches 1-4 & 6 are reserved and should be off, 5 is termination > power, 7 is HW compression (0-off,1-on), and 8 is SW > compression control > (0 lets host enable/disable compression, 1 disables host control). I > think the default is 0-6 off, 7 on , 8 off. The manual says it is > capable of either fixed or variable block sizes, it doesn't mention > anything about enabling/disabling it in hardware; it should be up to > the driver. Thanks for the detailed info about the dip switches. My manual lists all but DIP #7 as reserved. > > 3) Has anyone else using an AIT tape drive had similar problems? > > Not me. > > Did this problem recently start or have you never used it before? > Are the tapes new or old? > What is the exact error you're getting? > Can you tar or dump directly to and from the tape without errors? > OS and version? This problem existed ever since I tried to do my first resetore from tape. All of the tapes are less than 4 months old. I receive 2 error messages. When using amrecover, I receive an error message to stdout as follows: Extracting files using tape drive /dev/nst0 on host bender. Load tape BACKUP-22 now Continue [?/Y/n/s/t]? y ./r50/bin/MSFD_UTILITY.EXE ./r50/bin/PDM_SIMULATION_APPLICATION.EXE ./r50/bin/PGS_CRITERIA_VALIDATOR_DRIVER.EXE tar: Skipping to next header tar: Archive contains obsolescent base-64 headers tar: Error exit delayed from previous errors extract_list - child returned non-zero status: 2 Continue [?/Y/n/r]? y amrecover> exit 200 Good bye. The other message occurs in /tmp/amanda/amidxtaped debug file: amrestore: 8: restoring bender._rfss_ceesim_8k_lib-r50s.20040326.0 gzip: stdin: invalid compressed data--crc error gzip: stdin: invalid compressed data--length error amrestore: 9: reached end of information amidxtaped: time 294.174: amrestore terminated normally with status: 1 amidxtaped: time 294.174: rewinding tape ... amidxtaped: time 341.208: done amidxtaped: time 341.208: pid 25238 finish time Tue Apr 6 10:26:33 2004 -Rob
AIT-2
Hi, I'm currently having problems restoring files from my amanda backup system. I am able to narrow the problem down to my AIT-2 tape drive. If I restore files from amanda backups that are still on the holding disk, I have a successful restore. If I restore files from any of the AIT-2 tapes, I get tar errors. So I have a few questions: 1) When amanda uses tar to backup the data, what is the blocking size that amanda uses? 2) If anyone here is using an sdx-500 AIT-2 tape drive, what are your dip switches set to? (I'm wondering if I need to enable variable block sizing on the drive). 3) Has anyone else using an AIT tape drive had similar problems? Thanks -Rob
RE: amrecover question
I know that I can specify the tape device via CLI, or with settape in amrecover. I was curious why it's default value isn't set to /dev/st0, when: 1) it is listed in the man page as such 2) was compiled with that value when I passed the --with-tape-device=/dev/st0 parameter to ./configure -Rob > -Original Message- > From: Stefan G. Weichinger [mailto:[EMAIL PROTECTED] > Sent: Thursday, April 01, 2004 2:48 PM > To: '[EMAIL PROTECTED]' > Subject: Re: amrecover question > > > Hi, Robert, > > on Donnerstag, 01. April 2004 at 21:21 you wrote to amanda-users: > > DRC> What can I do to correctly set the default settape > variable in amrecover to /dev/st0? > > My amrecover tells me: > > Usage: amrecover [[-C] ] [-s ] [-t > ] [-d ] > > So it would work with: > > amrecover -d /dev/st0 > > If you roll your own binaries, you could configure your sources with > > configure --with-tape-device= /dev/st0 > > > -- > best regards, > Stefan > > Stefan G. Weichinger > mailto:[EMAIL PROTECTED] > > > > >
amrecover question
System Stats: Linux - 2.4.22 OS - RedHat 9.0 Amanda - 2.4.4p1 Question: According to the man page for amrecover, the settape default is set to /dev/st0 (my only tape device). However, when I run amrecover & extract, amrestore program fails. When I view the debug info, I see that amrecover passes a series of parameters to amrestore. But instead of passing the tape device (/dev/st0) to amrestore, it passes '0'. If I re-run amrecover, and specify settape /dev/st0 & then extract, amrestore successfully restores the data. What can I do to correctly set the default settape variable in amrecover to /dev/st0? -Rob
dumptypes
I noticed something odd today while maintaining my amanda server, and I seek some advise. My amanda server is slow (350MHz CPU), so most of the dump are configured so that the clients compress the data. The global dumptype is setup with "compress client best". For slower systems, I override the global compress with "compress client fast". But this doesn't seem to be working as of late. When I do a `ps -aef | grep amanda`, I see the dumper, the taper, and about 7-8 "gzip --best" processes. Now, in my disklist, I only have one entry for my amanda server, and 2 samba entries. All three use a dumptype that compresses client fast. All of my other systems listed in disklist are set for compress client best (linux, alpha, irix, solaris). So my question is, why am I seeing all of these gzip processes on the amanda server? I thought they were supposed to be residing on the client. Is there anyway to determine what system dump is causing the compression to reside on the server, instead of the client? Redhat 7.2 Linux 2.4.19 Amanda 2.4.2p2 -Rob
RE: multiple disklists
> Seems to be the strange-questions-day ;) ...
>
> Why not use two dumptypes?
>
> For example:
>
> > define dumptype important {
> > dumpcycle 2
> > priority high
> > }
>
> > define dumptype unimportant {
> > dumpcycle 5
> > priority low
> > }
I'm already using 2 different dumpcycles. My global config is to cycle 9
days. On the lower priority data, I have the dump cycle increased to 24
days.
Isn't there a way to share multiple disklists with a single config?
-Rob
RE: multiple disklists
Thanks for the info... I'll check it out.
-Rob
> -Original Message-
> From: Stefan G. Weichinger [mailto:[EMAIL PROTECTED]
> Sent: Thursday, January 22, 2004 11:14 AM
> To: Amanda List
> Subject: Re: multiple disklists
>
>
> Hi, Dege, Robert C.,
>
> on Donnerstag, 22. Jänner 2004 at 17:06 you wrote to amanda-users:
>
>
> DRC> Is there a way to have multiple disklists per config? I
> plan is to
> DRC> alternate the amdump cycles with the different
> disklists. I'm running into
> DRC> a tape space issue, and am trying to split my disklist
> into 2 disklists; one
> DRC> with lower priority backups & one with higher priority
> backups. The one
> DRC> with the lower priority would run like twice a week,
> while the higher
> DRC> priority disklist would run 5 times a week.
>
> Seems to be the strange-questions-day ;) ...
>
> Why not use two dumptypes?
>
> For example:
>
> > define dumptype important {
> > dumpcycle 2
> > priority high
> > }
>
> > define dumptype unimportant {
> > dumpcycle 5
> > priority low
> > }
>
> You get less lev0 for the "unimportant" stuff so you save space for
> the important ones.
>
> Let AMANDA schedule!
> --
> best regards,
> Stefan
>
> Stefan G. Weichinger
> mailto:[EMAIL PROTECTED]
>
>
>
multiple disklists
Is there a way to have multiple disklists per config? I plan is to alternate the amdump cycles with the different disklists. I'm running into a tape space issue, and am trying to split my disklist into 2 disklists; one with lower priority backups & one with higher priority backups. The one with the lower priority would run like twice a week, while the higher priority disklist would run 5 times a week. -Rob
Restore problem
Hi, I've appeared to run into a restore problem. I've been backing up several directories on a nightly basis using amanda for the past several months. Today, I had to restore a fairly large directory. About 1/3 through the restore, and error message appeared: tar: Skipping to next header tar: Archive contains obsolescent base-64 headers and the restore is no longer continuing. An added note, of all the times that I ran amdump, I never had any tar related errors in the email report. here are my specs: Linux: 2.4.22 Flavor: Redhat 9.0 Tar: 1.13.25 amanda: 2.4.4p1 -Rob
RE: Samba - which does compress-client-best point to?
Thanks for the info Paul (and Jay). Paul, a few additional questions directed towards your response. > In my experience the compress best uses 4 times as much CPU for only > 5% better compression, so it's not worth it, unless you have spare CPU > cycles to burn. Maybe it's better to increase the dumpcycle (maybe Is this 5% difference you're referring to between compress-fast vs. compress-best? > Right. If you think a litter more about this, the amanda server does > not need to be the computer that runs smbclient. My amandaserver has > already his cpu fully loaded, and two other machines do the smbclient > backups for my window machines, and they do the compression too. How could I offload the smbclient connections through another machine? Are you implying an smbmount on the client, or is there some trick with smbclient that I'm not thinking of right now? -Rob
Samba - which does compress-client-best point to?
System: RedHat 7.1, kernel 2.4.19 amanda 2.4.2p2, samba 2.2.6 I've been backing up several Windows machines for a while now (months). Recently, I've been getting cramped with tape space, so I added "compress-client-best" to my samba-pc dump type. However, while watching amanda perform the dump, it seems as if the linux server is compressing the data, and not the windows client. The more I think about it, the more it makes sense, since amanda treats the smbclient connection as an ftp connection rather than an amanda client machine. So the amanda server itself is the client, and the server in one for the samba backups (right?) But, my amanda server is slow. So the PC stays connected while the dumper compresses the dumped files. Would the dumper relinquish the machine faster if I used compress-svr-fast vs. compress-client-fast? -Rob
RE: amverify errors
/bin/gtar -> /bin/tar, as it does on all the other machines. If that were the case, wouldn't it have problems performing the backup, or is that mixed in with runtar? -Rob -Original Message- From: Jon LaBadie [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 24, 2003 3:38 PM To: '[EMAIL PROTECTED]' Subject: Re: amverify errors On Wed, Sep 24, 2003 at 06:34:20AM -0700, Dege, Robert C. wrote: > > I'm running amanda-2.4.2p2-7 (a default RedHat 7.3 rpm). > > When doing an amverify after an amdump, I receive the following messages & > was wondering why: > > Skipped bast._devel_digital.20030903.1 (** Cannot do /bin/gtar dumps) > Skipped bast._devel_dev__grp__db.20030903.4 (** Cannot do /bin/gtar dumps) > Skipped bast._devel_dev__grp.20030903.1 (** Cannot do /bin/gtar dumps) > Skipped bast._devel_base.20030903.2 (** Cannot do /bin/gtar dumps) > Skipped bast._devel_upi.20030903.1 (** Cannot do /bin/gtar dumps) > > This only occurs on the machine bast. All of the other machines in my > disklist are checked correctly, and they also use /bin/gtar when amdump is > run. Just a possibility, is gtar in a different location on that machine? -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
amverify errors
I'm running amanda-2.4.2p2-7 (a default RedHat 7.3 rpm). When doing an amverify after an amdump, I receive the following messages & was wondering why: Skipped bast._devel_digital.20030903.1 (** Cannot do /bin/gtar dumps) Skipped bast._devel_dev__grp__db.20030903.4 (** Cannot do /bin/gtar dumps) Skipped bast._devel_dev__grp.20030903.1 (** Cannot do /bin/gtar dumps) Skipped bast._devel_base.20030903.2 (** Cannot do /bin/gtar dumps) Skipped bast._devel_upi.20030903.1 (** Cannot do /bin/gtar dumps) This only occurs on the machine bast. All of the other machines in my disklist are checked correctly, and they also use /bin/gtar when amdump is run. -Rob
RE: Dumps Levels > 1?
Thank you for the suggestions. I'll checkout the bumpsize, bumpmult, and bumpdays & report my findings. -Rob -Original Message- From: Jon LaBadie [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 02, 2003 12:47 PM To: [EMAIL PROTECTED] Subject: Re: Dumps Levels > 1? On Tue, Sep 02, 2003 at 11:36:40AM -0500, Chris Johnson wrote: > you'll need to work with the "bumpsize" and "bumpmult" entries in > amanada.conf. > mine are set to 100Mb and 2 respectivly. This seems to give me level 3 > or 4 on my heavily used filesystems for most of the week. > "bumpdays" may be a factor here as well. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Dumps Levels > 1?
My config: Redhat 9.0 Amanda version 2.4.4p1 I'm slightly concerned with my backups. I'm backingup a central NFS server for my UNIX network. Using disklist, I broke the NFS share into 21 separate sections. I did this so that I could benefit from higher dump levels on sections that are used less. I've been running amanda for the past 2 weeks, but only have dump levels of zero, or one. I ran 2 backups over labor day weekend, and _STILL_ am unable to achieve a dump level higher than 1. And the amreports show no dump level bump adjustments. I guess my question is "why isn't amanda using higher dump levels on sections where the data hasn't changed?" -Rob
RE: Amanda Printing error
When I originally compiled/installed amanda, I didn't have the LPRng rpm installed. As a result, amanda left LPRCMD and LPRFLAG undef. Since the compile, I have installed & configured printing. Is there anyway to implement it without have to re-run configure & re-install the amanda binaries on my system?? (btw, thanks for the indepth info :) -Rob -Original Message- From: Jon LaBadie [mailto:[EMAIL PROTECTED] Sent: Thursday, August 07, 2003 9:58 AM To: '[EMAIL PROTECTED]' Subject: Re: Amanda Printing error On Thu, Aug 07, 2003 at 06:38:41AM -0700, Dege, Robert C. wrote: > > Yes, the lbl-template is defined in the tapetype. I also defined the > printer="lp", but it didn't seem to help. > > -Rob > > -Original Message- > From: Jon LaBadie [mailto:[EMAIL PROTECTED] > Sent: Thursday, August 07, 2003 9:22 AM > To: Amanda List (E-mail) > Subject: Re: Amanda Printing error > > > On Thu, Aug 07, 2003 at 05:59:11AM -0700, Dege, Robert C. wrote: > > > > I just installed amanda-2.4.4p1, and am getting this error message: > > > > amreport: ERROR no printer command defined > > > > Backups are still being done however. Any ideas why I'm gettign this? > > Do you have lbl-template defined? > If so, it is trying to print a tape label and doesn't know how. > Its funny, I have lbl-template defined and I get a printing after each amdump/amreport. Yet I don't have a printer definition in any of my config files. However, I see in my config/config.h file that configure found a printer command and the option to specify a printer name. They are set as "LPRCMD" and "LPRFLAG" in the config.h file to "/usr/bin/lp" and "-d" respectively. I'm guessing now that the printer directive in the tapetype is used to specify a printer "name", not command, in case the printer you want to print to is not the default. In that case the LPRFLAG would be used with the printer name as "/usr/bin/lp -d " and I could print to any of my several printers. But the above is just a guess, untried and I haven't looked it up in the docs or the source. Check that your config.h file has reasonable definition for LPRCMD and LPRFLAG and try either leaving out the printer definition or specifying a printer name. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
amrecover
Okay, I've got a problem here. I running amanda-2.4.4p1 on a linux Redhat 9.0, with a tape changer connected directly to the machine. I'm trying to restore a few directories, and am having problems getting the amrecover to work. After I set host, disk, date, and extraction list, I start the extract, but it fails. When looking at the logs, it tells me the following: amrestore: could not stat 0: No such file or directory amidxtaped: time 0.041: amrestore terminated normally with status: 2 amidxtaped: could not stat 0: No such file or directory amidxtaped: time 0.042: could not stat 0: No such file or directory amidxtaped: time 0.042: pid 1305 finish time Mon Aug 11 09:54:03 2003 I'm assuming that this refers to config "0" in chg-scsi.conf. So I set the settape to /dev/st0, and rerun extract. Now I get this error: changer: got exit: 2 str: could not read result from "/usr/local/amanda/libexec/chg-scsi" amidxtaped: could not get changer info: could not read result from "/usr/local/amanda/libexec/chg-scsi" amidxtaped: time 0.067: could not get changer info: could not read result from "/usr/local/amanda/libexec/chg-scsi" amidxtaped: time 0.067: pid 1268 finish time Mon Aug 11 09:47:55 2003 So I figure this is a result of amrecover trying to read the amanda.conf file & trying to talk with the tape changer using the /dev/st0 I specified when I did a settape. So I change settape to /dev/sg0 (the tpae changer). Now I get this error: amrestore: Could not rewind device '/dev/sg0': tape_rewind: rewinding tape: /dev/sg0: Operation not permitted amidxtaped: time 30.127: amrestore terminated normally with status: 2 amidxtaped: time 30.128: rewinding tape ... amidxtaped: time 60.226: tape_rewind: rewinding tape: /dev/sg0: Operation not permitted amidxtaped: time 60.226: pid 1272 finish time Mon Aug 11 09:50:42 2003 What do I have to do to get data from a restore tape??? I have reports showing the data was backed up, so I know the data is there. -Rob
RE: amrecover
Okay, that seems to be working now. Is there a way to change the default tape value in amrecover so that it doesn't set itself to "0"? Also, can you run multiple amrecover sessions against the same config if you have multiple tape drives that you can specify? Not sure if there would be a file locking issue with the indexing DB. -Rob -Original Message- From: Frank Smith [mailto:[EMAIL PROTECTED] Sent: Monday, August 11, 2003 11:11 AM To: Dege, Robert C.; Amanda List (E-mail) Subject: Re: amrecover Amanda always expect the no-rewind device (/dev/nst0) so that the tape remains in the correct position for the next read or write. Chances are it is reading the header, rewinding, and then not finding a dump image. Frank
RE: Amanda Printing error
Yes, the lbl-template is defined in the tapetype. I also defined the printer="lp", but it didn't seem to help. -Rob -Original Message- From: Jon LaBadie [mailto:[EMAIL PROTECTED] Sent: Thursday, August 07, 2003 9:22 AM To: Amanda List (E-mail) Subject: Re: Amanda Printing error On Thu, Aug 07, 2003 at 05:59:11AM -0700, Dege, Robert C. wrote: > > I just installed amanda-2.4.4p1, and am getting this error message: > > amreport: ERROR no printer command defined > > Backups are still being done however. Any ideas why I'm gettign this? Do you have lbl-template defined? If so, it is trying to print a tape label and doesn't know how. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
amanda.conf
I have a few dquestions regarding the new config optinos in amanda.conf for 2.4.4p1: dumpuser - how does the format work? default shows sssS, and a commented BTBTBTBTBTBT. Is there a set length for the string? is there a significance in string length?, etc. autoflush - I don't completely understand it's benefit. Is this meant to cleanup older dumps during the next amdump run? -Rob
Amanda Printing error
I just installed amanda-2.4.4p1, and am getting this error message: amreport: ERROR no printer command defined Backups are still being done however. Any ideas why I'm gettign this? -Rob
Printing reports
I'm trying to configure amanda so that it will printout daily reports when
amdump runs.
I have the following in my amanda.conf:
printer "ls"
define tapetype AIT-2 {
comment "SDX-500C with 50GB cartridge."
length 54538 mbytes
filemark 1541 kbytes
speed 2920 kps
lbl-templ "/usr/local/amanda/configs/reports.ps"
}
When I run amcheck, I get the following error:
ERROR: lbl_templ set but no printer defined
I am able to run lpr from the CLI & print to my printer, and there is no
debugging info explaining why it's not working.
Any ideas?
-Rob
Where oh where is chg-scsi?
I have a Quantum PowerStor L200 Disk Changer with a Quantum DLT8000 tape drive builtin. It is connected to an alpha running TRU64 5.1A. Now that I have my specs out of the way, lemme explain my problem. This is my first time setting up an amanda server, so I made sure to read the docs to the best of my ability. As I built & configured amanda, I decided that chg-scsi would be the best choice to interact with the tape changer. However, after I finished configuring the device, chg-scsi.conf, and amanda.conf, I discover that the chg-scsi binary was never built or installed into libexec. Based on the TapeChanger doc, chg-scsi seemed to be best suited for my hardware configuration. But now that it's not there, my next best option is to use the chg-multi. I was curious why chg-scsi was never built, or if I configured something incorrectly. I listed my configure paramters below: ./configure CFLAGS="-O4 -fast -tune=ev6" CPPFLAGS="-O4 -fast -tune=ev6" --prefix=/usr/local/amanda --with-configdir=/usr/local/amanda/configs --with-suffixes=no --with-index-server=fe-server --with-user=amanda --with-group=amanda --with-config=fe_nightly --with-tape-device=/dev/ntape/tape2 --with-changer-device=/dev/changer/mc1 --with-gnutar=/usr/local/bin/tar --with-mmap --with-buffered-dump -Rob
