Amanda configuration, vxfs and ClearCase
Hi folks! I have some questions about setting up Amanda environment with vxfs and ClearCase (CC) support: 1. We don't want to install a compiler on the CC server (Amanda client) and therefore need to compile the client on the same host as the Amanda server. Both are SPARC runnig Solaris 7. The problem is that the client (CC server) use vxfs for some file system and vxfs is not present on the Amanda server. Will Amanda build ok (with vxfs support) if I copy the /usr/lib/fs/vxfs dir from the CC server to Amanda server? 2. Which files/directories needs to be on the client as a minimum to function properly? Remember that I don't want to build on the client directly nor want to use an NFS share. 3. To successfully back up a CC server, the VOBs needs to be locked. This is normally done with a script. How can I force the client to run a script before (and after to unlock the VOBs) backup is executed? Thanks in advance! --Peres-- Per Sverre Stiansen, System Administrator. Oslo ATCC Norwegian Air Traffic and Airport Management, NATAM
Re: Linux (Debian) and large files?
On Sun, 4 Feb 2001, Stan Brown wrote: I am fixing to move a fair sized Amanda site from HP-UX to Linux (Debian Potato) for it;s tapehost. I have files 2G, what special things do I need to do to make the Linux machine handle these largefiles? You may use a kernel-enterprise for that. It also supports Terabytes of memmory. -- Stan Brown [EMAIL PROTECTED]843-745-3154 Charleston SC. -- Windows 98: n. useless extension to a minor patch release for 32-bit extensions and a graphical shell for a 16-bit patch to an 8-bit operating system originally coded for a 4-bit microprocessor, written by a 2-bit company that can't stand for 1 bit of competition. - (c) 2000 Stan Brown. Redistribution via the Microsoft Network is prohibited. Cheers, -- Renato Santana
Re: Amanda configuration, vxfs and ClearCase
"Stiansen, Per Sverre" [EMAIL PROTECTED] writes: 3. To successfully back up a CC server, the VOBs needs to be locked. This is normally done with a script. How can I force the client to run a script before (and after to unlock the VOBs) backup is executed? You build amanda --with-gnutar=/usr/local/sbin/gnutar-for-amanda (your choice of name, of course), then write a script that, on the outside, behaves like GNU tar, but on the inside does ClearCase magic when required. I can send a Deeply Ugly one, if necessary. Will
RE: Amanda configuration, vxfs and ClearCase
Ok, maybe I'm slow but I need some deeper explanation to this. I believed
that Amanda picked up the right dump program to use depending on what kind
of fs present on the actual partition/device i.e vxdump on vxfs and ufsdump
on ufs (Solaris). If compiled with --with-gnutar=fileref option, how can
Amanda still work with vxdump/ufsdump? How will the disklist amanda.conf
(define dumptype global part) file look like for such configuration? The CC
script to call before backup is path/vob_standard.sh lock ("lock" as
argument) and after backup is finished, path/vob_standard.sh unlock (this
could be two different scripts like lock.sh an unlock.sh if easier)
--Peres--
-Opprinnelig melding-
Fra: Will Partain [mailto:[EMAIL PROTECTED]]
Sendt: 5. februar 2001 13:23
Til: [EMAIL PROTECTED]
Emne: Re: Amanda configuration, vxfs and ClearCase
"Stiansen, Per Sverre" [EMAIL PROTECTED] writes:
3. To successfully back up a CC server, the VOBs
needs to be locked. This is normally done with a script.
How can I force the client to run a script before (and
after to unlock the VOBs) backup is executed?
You build amanda --with-gnutar=/usr/local/sbin/gnutar-for-amanda
(your choice of name, of course), then write a script that,
on the outside, behaves like GNU tar, but on the inside does
ClearCase magic when required. I can send a Deeply Ugly
one, if necessary.
Will
Linux setup problems
I'm just seting up my first Linux (Debian Potato) box in a while. Eventually it will be a tapehost, but tirght now I'm just trying to set it up as a client. Compile, and install went well, and i got /etc/services, and inetd.conf set up corectly (I think). However I am getting a premissions error: Amanda Backup Client Hosts Check ERROR: debian: [can not access /dev/hdc1 (hdc1): Permission denied] ERROR: debian: [can not access /dev/hda1 (hda1): Permission denied] ERROR: debian: [can not access /dev/hda3 (hda3): Permission denied] ERROR: debian: [can not read/write /etc/dumpdates: No such file or directory] Client check: 20 hosts checked in 0.545 seconds, 4 problems found Here are the premissions of the executables: -rwxr-xr-x1 amanda disk 337250 Feb 5 05:05 amadmin -rwsr-x---1 root disk 345638 Feb 5 05:05 amcheck -rwxr-xr-x1 amanda disk 1861 Feb 5 05:05 amcheckdb -rwxr-xr-x1 amanda disk 3962 Feb 5 05:05 amcleanup -rwxr-xr-x1 amanda disk 3556 Feb 5 05:05 amdump -rwxr-xr-x1 amanda disk 317114 Feb 5 05:05 amflush -rwxr-xr-x1 amanda disk 122193 Feb 5 05:05 amgetconf -rwxr-xr-x1 amanda disk 261066 Feb 5 05:05 amlabel -rwxr-xr-x1 amanda disk 4191 Feb 5 05:06 amoverview -rwxr-xr-x1 amanda disk 4482 Feb 5 05:06 amplot -rwxr-x---1 amanda disk 292191 Feb 5 05:06 amrecover -rwxr-xr-x1 amanda disk 293332 Feb 5 05:05 amreport -rwxr-xr-x1 amanda disk 171745 Feb 5 05:06 amrestore -rwxr-xr-x1 amanda disk 6461 Feb 5 05:06 amrmtape -rwxr-xr-x1 amanda disk20386 Feb 5 05:06 amstatus -rwxr-xr-x1 amanda disk 270070 Feb 5 05:05 amtape -rwxr-xr-x1 amanda disk 6587 Feb 5 05:06 amtoc -rwxr-xr-x1 amanda disk11510 Feb 5 05:06 amverify And here are the permissions on the disks: brw-rw1 root disk 3, 1 Nov 30 10:22 /dev/hda1 What have I got wrong? -- Stan Brown [EMAIL PROTECTED]843-745-3154 Charleston SC. -- Windows 98: n. useless extension to a minor patch release for 32-bit extensions and a graphical shell for a 16-bit patch to an 8-bit operating system originally coded for a 4-bit microprocessor, written by a 2-bit company that can't stand for 1 bit of competition. - (c) 2000 Stan Brown. Redistribution via the Microsoft Network is prohibited.
problem with backup-configuration
Hello to all of the Amanda specialists and users. Once more i have got a problem with amanda. I wish to implement a backup starts at a friday with the full backup, then Monday - Thursday the smaller backups.So one cycle runs a week and need 5 dumps. For security i want to use two cycles, so i need 10 tapes before overwriting old tapes. I thought i can configure that in amanda.conf (dumpcycle 2 weeks, runspercycle 10, typecycle 12 because 10 are needed and 2 as reserve). I have to test it and so i tried the following:dumpcycle 3 days, runspercycle 3, typecycle 3. My intention by this was i have 3 tapes called csd01,csd02,csd03. The first backup had to be full on csd01, the next 2 should me smaller (on first on csd02 then on csd03). The fourth backup should be a full backup on tape csd01 again. The next on csd02 . For the tests i tried to use only one cycle and i start the backup ervery 10min. But i doesen't work like i thought. First the succession doesn't match. Sometimes e.g. tape csd06 has to be used were tape csd03 is expected. And why tape 06 when i have only tape csd01 till tape csd06. And the full backup comes sometimes on csd03 I've changed amanda.conf. First i made tests with 6 tapes, but for the test i had only 3 so i changed amanda.conf I didn't find ansers to the problem in FAQ or other descriptions. Thanks for help With kind regards Frank
Re: Linux setup problems
On Mon, Feb 05, 2001 at 10:50:45AM -0500, Stan Brown wrote: I'm just seting up my first Linux (Debian Potato) box in a while. Eventually it will be a tapehost, but tirght now I'm just trying to set it up as a client. Compile, and install went well, and i got /etc/services, and inetd.conf set up corectly (I think). However I am getting a premissions error: Amanda Backup Client Hosts Check ERROR: debian: [can not access /dev/hdc1 (hdc1): Permission denied] ERROR: debian: [can not access /dev/hda1 (hda1): Permission denied] ERROR: debian: [can not access /dev/hda3 (hda3): Permission denied] ERROR: debian: [can not read/write /etc/dumpdates: No such file or directory] Client check: 20 hosts checked in 0.545 seconds, 4 problems found Here are the premissions of the executables: -rwxr-xr-x1 amanda disk 337250 Feb 5 05:05 amadmin -rwsr-x---1 root disk 345638 Feb 5 05:05 amcheck -rwxr-xr-x1 amanda disk 1861 Feb 5 05:05 amcheckdb -rwxr-xr-x1 amanda disk 3962 Feb 5 05:05 amcleanup -rwxr-xr-x1 amanda disk 3556 Feb 5 05:05 amdump -rwxr-xr-x1 amanda disk 317114 Feb 5 05:05 amflush -rwxr-xr-x1 amanda disk 122193 Feb 5 05:05 amgetconf -rwxr-xr-x1 amanda disk 261066 Feb 5 05:05 amlabel -rwxr-xr-x1 amanda disk 4191 Feb 5 05:06 amoverview -rwxr-xr-x1 amanda disk 4482 Feb 5 05:06 amplot -rwxr-x---1 amanda disk 292191 Feb 5 05:06 amrecover -rwxr-xr-x1 amanda disk 293332 Feb 5 05:05 amreport -rwxr-xr-x1 amanda disk 171745 Feb 5 05:06 amrestore -rwxr-xr-x1 amanda disk 6461 Feb 5 05:06 amrmtape -rwxr-xr-x1 amanda disk20386 Feb 5 05:06 amstatus -rwxr-xr-x1 amanda disk 270070 Feb 5 05:05 amtape -rwxr-xr-x1 amanda disk 6587 Feb 5 05:06 amtoc -rwxr-xr-x1 amanda disk11510 Feb 5 05:06 amverify And here are the permissions on the disks: brw-rw1 root disk 3, 1 Nov 30 10:22 /dev/hda1 What have I got wrong? Is amanda a member of group disk? (it's not sufficient for the executables to belong to group disk, unless they are setgid (and I'm not sure that would be desirable)) -ron
Re: Strange dump summary...
BTW, I can backup "/etc" filesystem using dump on the client machines. But no luck from Amanda server. Can you do those backups as the Amanda user? Is the group that owns the disks the primary Amanda user group or an alternate? If an alternate and you're using xinetd, are you using the option that has it set up the group membership (the default is to only run services with the primary group, not the alternates)? Suman John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: Linux (Debian) and large files?
On Mon Feb 5 06:26:41 2001 Renato R. Santana wrote... On Sun, 4 Feb 2001, Stan Brown wrote: I am fixing to move a fair sized Amanda site from HP-UX to Linux (Debian Potato) for it;s tapehost. I have files 2G, what special things do I need to do to make the Linux machine handle these largefiles? You may use a kernel-enterprise for that. It also supports Terabytes of memmory. Sorry, I am not familair with what a "kernel-enterprise" is. Can you enlighten me? -- Stan Brown [EMAIL PROTECTED]843-745-3154 Charleston SC. -- Windows 98: n. useless extension to a minor patch release for 32-bit extensions and a graphical shell for a 16-bit patch to an 8-bit operating system originally coded for a 4-bit microprocessor, written by a 2-bit company that can't stand for 1 bit of competition. - (c) 2000 Stan Brown. Redistribution via the Microsoft Network is prohibited.
Re: amrestore simple question
I am having problems restoring. I run amrestore /dev/nst0 machine.kuku.com /site | restore -i but it doesnt look right. What am I doing wrong ? I don't know. You didn't give any where near enough information to be able to help. What problems are you having? What "doesnt look right"? What version of Amanda are you using? I do notice that you're trying to pipe the output of amrestore into restore, but don't appear to have the "-p" option on amrestore. Without that, it will bring back the image to a file in your current directory. Tal John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: Linux (Debian) and large files?
On Mon, 5 Feb 2001, Stan Brown wrote: On Mon Feb 5 06:26:41 2001 Renato R. Santana wrote... On Sun, 4 Feb 2001, Stan Brown wrote: I am fixing to move a fair sized Amanda site from HP-UX to Linux (Debian Potato) for it;s tapehost. I have files 2G, what special things do I need to do to make the Linux machine handle these largefiles? You may use a kernel-enterprise for that. It also supports Terabytes of memmory. Sorry, I am not familair with what a "kernel-enterprise" is. Can you enlighten me? Sure. This kernel version includes a kernel that has appropriate configuration options enabled for the typical large enterprise server. This includes SMP support for multiple processor machines, support for large memory configurations, support for large file I/O, and other appropriate items. Look for a package called kernel-enterprise. If your distribution does not have it, try www.rpmfind.com (looking for "kernel-enterprise"). -- Stan Brown [EMAIL PROTECTED]843-745-3154 Charleston SC. -- Windows 98: n. useless extension to a minor patch release for 32-bit extensions and a graphical shell for a 16-bit patch to an 8-bit operating system originally coded for a 4-bit microprocessor, written by a 2-bit company that can't stand for 1 bit of competition. - (c) 2000 Stan Brown. Redistribution via the Microsoft Network is prohibited. Cheers, -- Renato Santana
Re: Missing e-mail reports
but this means the man-pages are wrong. You mean you actually read them??? :-) Fixed. Thanks. Gerhard John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: Amanda CAN'T SWITCH TO INCREMENTAL MODE
I just reinstalled Amanda-2.4.1 on FreeBSD-4.2-STABLE and nuked the = curinfo, log* and amdump* files from /usr/local/etc/amanda/config=20 Any particular reason you didn't go with 2.4.2p1? Yes, I fetched the 2.4.2p1 source and during the 'make check' and make it bombed with error message: make: don't know how to make amoverview did't have a lot of time to figure this out so I rolled back to 2.4.1p1 I went ahead and started a new install and did the config files as usual = but whe I run amdump amanda always says "CAN'T SWITCH TO INCREMENTAL = DUMP". ... taper: FATAL shmget: Cannot allocate memory The last line from taper is the important part. It says that when taper tried to allocate some shared memory with shmget, the OS told it "no". Is shared memory an option you have to build into your kernel? Or add some kernel config option to enable or set the size? If you run "ipcs -a" do you see any shared memory segments allocated to the Amanda user? If so, they may be leftovers from testing you did and need to be removed (ipcrm). Ok, there are a few amanda owned shared mems here and I removed them all P.S. Please turn off "send as HTML" in your mailer. It's just annoying Sorry! -- no excuse here :( Dan
Re: Amanda CAN'T SWITCH TO INCREMENTAL MODE
Yes, I fetched the 2.4.2p1 source and during the 'make check' and make it bombed with error message: make: don't know how to make amoverview That's a bug in your version of make. Here's the latest from David Wolfskill ([EMAIL PROTECTED]) who's tracked it the closest: Summarizing: either installing GNU make (from /usr/ports/devel/gmake) and using gmake to build amanda, or patching the native FreeBSD make per http://www.FreeBSD.org/cgi/query-pr.cgi?pr=24102 should do the trick for you. And regardless of which approach you tak, please update http://www.freebsd.org/cgi/query-pr.cgi?pr=23328 to let folks know that action to resolve this would be helpful. (If you need to modify the patches in http://www.FreeBSD.org/cgi/query-pr.cgi?pr=24102 for 4.2-R, it would be good to follow up on that, as well.) Dan John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: Missing e-mail reports
* John R. Jackson [EMAIL PROTECTED] (Mon, Feb 05, 2001 at 01:30:50PM -0500) but this means the man-pages are wrong. You mean you actually read them??? :-) yes, actually I did, and as I noticed, not good enough, quite a lot of stuff asked here is actually answered in the manpages or in the FAQ (if you know where to look ;) ) [like my question about dumpcycle/tapecycle from a few weeks back] Gerhard, @jasongeo.com == The Acoustic Motorbiker == -- __O Standing above the crowd, he had a voice so strong and loud =`\, we'll miss him (=)/(=) Ranting and pointing his finger, At everything but his heart we'll miss him
Re: Linux (Debian) and large files?
Hi, sorry to interupt,but debian does not use rpm packageformat. it has it own format called dpkg, so www.rpmfind.com is a bad idea... all he has to do, is setting chunksize to something like 2000 MB (NOT 2GB, that won't work) have a nice day Christoph "Renato R. Santana" schrieb: On Mon, 5 Feb 2001, Stan Brown wrote: On Mon Feb 5 06:26:41 2001 Renato R. Santana wrote... On Sun, 4 Feb 2001, Stan Brown wrote: I am fixing to move a fair sized Amanda site from HP-UX to Linux (Debian Potato) for it;s tapehost. I have files 2G, what special things do I need to do to make the Linux machine handle these largefiles? You may use a kernel-enterprise for that. It also supports Terabytes of memmory. Sorry, I am not familair with what a "kernel-enterprise" is. Can you enlighten me? Sure. This kernel version includes a kernel that has appropriate configuration options enabled for the typical large enterprise server. This includes SMP support for multiple processor machines, support for large memory configurations, support for large file I/O, and other appropriate items. Look for a package called kernel-enterprise. If your distribution does not have it, try www.rpmfind.com (looking for "kernel-enterprise"). -- Stan Brown [EMAIL PROTECTED]843-745-3154 Charleston SC. -- Windows 98: n. useless extension to a minor patch release for 32-bit extensions and a graphical shell for a 16-bit patch to an 8-bit operating system originally coded for a 4-bit microprocessor, written by a 2-bit company that can't stand for 1 bit of competition. - (c) 2000 Stan Brown. Redistribution via the Microsoft Network is prohibited. Cheers, -- Renato Santana
disk is off line
I get this msg when I try backing up a machine (Linux 7.0) I have setup xinetd, groups, .amandahosts, I even changed permission on /dev of the client, but still no go. Any ideas ? -- Tal Ovadia Jalan Network Services Inc. Phone: (818)-597-6301 --- Why Oh Why didn't I take the Blue Pill...
server crashes
I just implemented amanda to backup about 12 clients and so far amanda has run twice. Each time amdump runs on the server, one of the clients (a freebsd 4.0 box) completely hangs without an error in the /var/log/messages. I have not found any logs to tell me what broke when I ran a backup. Does anyone have an idea about what is wrong or what I should check? Thanks in advance. Ryan Williams
Amanda Client on FreeBSD
Hi all, Checked out the FAQ-o-matic and nothing there, s I have an Amanda 2.4.2 client set to backup the /home of a FreeBSD client. When I run amcheck on the index server (Red Hat 6.2), it comes back saying 'permission denied' to access the /home partition. The partition is owned by root.wheel, 755 perms, and dump is suid on the FreeBSD box. User amanda has been added to the wheel group. Any ideas? Thanks Shawn Shawn M. GreenSr. Systems Administrator Teja Technologies, Inc. [EMAIL PROTECTED]
Re: Amanda Client on FreeBSD
I have an Amanda 2.4.2 client set to backup the /home of a FreeBSD client. When I run amcheck on the index server (Red Hat 6.2), it comes back saying 'permission denied' to access the /home partition. I assume what you mean is it said permission denied trying to access something or other in /dev, right? The partition is owned by root.wheel, 755 perms ... Again, I assume you mean the /dev for the partition? Any chance one of the parent directories is blocking access? and dump is suid on the FreeBSD box. ... Which is not relevant. It is only setuid because of the insanely stupid way they (and most dump vendors) start the rmt protocol. It drops its permissions right after startup, so has no more access than the calling (Amanda) user. User amanda has been added to the wheel group. So if you run something like this on the client: su amanda-user -c "dump 9f - /home /dev/null" (whatever you dump program is called) does it work? Is Amanda using dump or GNU tar? Are you running xinetd on the client? Did you use "groups yes" in the amandad entry so xinetd gives the child all the alternate groups? Did amcheck report the correct device that you think maps to /home? In other words, is /etc/fstab (or whatever your system uses) correct? If none of this helps, please post the exact messages from amcheck and a "ls -lL" of the items it says have a permission problem. Shawn John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
gzip
I have 2 questions relating to gzip. 1. I have all of my gzips set to fast instead of best but whenever amdump is running there will be a gzip --fast and gzip --best for every file that is in my holding disk. What are the reasons behind this? 2. quoting a colocation facilitys website: "We use bzip2 instead of gzip for data compression. Unlike gzip, bzip2 compresses data in blocks, which means that in the unlikely event that a small part of the backup is corrupted, only the affected block is lost. All other data is still recoverable." Is this true and if so is there a way to use bzip instead of gzip? Has anyone ever looked into this? Thanks, Ryan Williams
Re: problem with backup-configuration
... I wish to implement a backup starts at a friday with the full backup, then Monday - Thursday the smaller backups. ... Why do you want such a rigid schedule? Amanda normally does things by balancing the load (which means shifting full and partial dumps around) through the dumpcycle. Is there some reason you need to force it into a particular pattern? This is a very common issue for new Amanda users to have trouble with (I certainly did when I started). The traditional method of "it's Tuesday so this is what's going to happen" is based on ease of implementation, a major goal of all administrators :-). But Amanda, being a computer program, can be much smarter than an administrator (scary, but true :-) and so do things a "better" way. So one cycle runs a week and need 5 dumps. For security i want to use two cycles, so i need 10 tapes before overwriting old tapes. OK. I thought i can configure that in amanda.conf (dumpcycle 2 weeks, runspercycle 10, typecycle 12 because 10 are needed and 2 as reserve). If you want a full dump every week, dumpcycle should be 1 week, not two, and runspercycle would then be 5. I assume you really have 12 tapes? Whether you do or not, tapecycle should be the actual number of tapes. I have to test it and so i tried the following:dumpcycle 3 days, runspercycle 3, typecycle 3. My intention by this was i have 3 tapes called csd01,csd02,csd03. The first backup had to be full on csd01, the next 2 should me smaller (on first on csd02 then on csd03). The fourth backup should be a full backup on tape csd01 again. ... See above about the rigid schedule. What Amanda probably tried to do was move some of the full dumps to the other tapes. ... Sometimes e.g. tape csd06 has to be used were tape csd03 is expected. ... Amanda would only have asked for csd06 (or anything beyond csd03) if you told it about those tapes, i.e. did an amlabel and/or set the tapecyle higher than three. For your testing, you may need to wipe out the tapelist file as part of making Amanda forget what you tried before. Frank John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: Amanda Client on FreeBSD
First off, I just want to start this out saying that I am not an expert at this by far but I have read the chapter from backup central about 5 times so that I would understand what I am doing. Please correct me if I am wrong at anything here. I just recently installed amanda on about 15 freebsd boxes so I feel I could do it in my sleep now :). In freebsd you must add amanda to the group operators. (edit /etc/group and after root on the group operators put ,amanda so it looks like root,amanda) You don't use the directory's when telling it what to backup, atleast not in my experience. You would have to be root to do so even if it was allowed (i think). Type `df` at a prompt and it will tell you all of your partitions. It should come out something like the following: Filesystem 1K-blocks UsedAvail Capacity Mounted on /dev/ad0s1a 4958336173 944479%/ /dev/ad0s1f 5425485 3993979 99746880%/usr /dev/ad0s1e496111 323299 13312471%/var procfs 440 100%/proc If you want to backup the user partition, you would stick ad0s1f from that example into your disklist and not usr. - Original Message - From: "John R. Jackson" [EMAIL PROTECTED] To: "Shawn M. Green" [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Monday, February 05, 2001 11:18 PM Subject: Re: Amanda Client on FreeBSD I have an Amanda 2.4.2 client set to backup the /home of a FreeBSD client. When I run amcheck on the index server (Red Hat 6.2), it comes back saying 'permission denied' to access the /home partition. I assume what you mean is it said permission denied trying to access something or other in /dev, right? The partition is owned by root.wheel, 755 perms ... Again, I assume you mean the /dev for the partition? Any chance one of the parent directories is blocking access? and dump is suid on the FreeBSD box. ... Which is not relevant. It is only setuid because of the insanely stupid way they (and most dump vendors) start the rmt protocol. It drops its permissions right after startup, so has no more access than the calling (Amanda) user. User amanda has been added to the wheel group. So if you run something like this on the client: su amanda-user -c "dump 9f - /home /dev/null" (whatever you dump program is called) does it work? Is Amanda using dump or GNU tar? Are you running xinetd on the client? Did you use "groups yes" in the amandad entry so xinetd gives the child all the alternate groups? Did amcheck report the correct device that you think maps to /home? In other words, is /etc/fstab (or whatever your system uses) correct? If none of this helps, please post the exact messages from amcheck and a "ls -lL" of the items it says have a permission problem. Shawn John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: server crashes
... Each time amdump runs on the server, one of the clients (a freebsd 4.0 box) completely hangs without an error in the /var/log/messages. I have not found any logs to tell me what broke when I ran a backup. Does anyone have an idea about what is wrong or what I should check? This is all guesswork because I don't run FreeBSD, but that's never stopped me from shooting off my E-mouth before :-): * It could be any number of hardware problems, including the disk being backed up, the cable, the controller, seating of any of the things that move, bad termination, bad option switch settings, speed mismatches (SCSI-2 on a SCSI-1 bus), bad firmware, bad DMA control to/from memory, bad memory, etc. It could also be any of the above with the network interface rather than the disk. * It could be a kernel problem dealing with a hardware problem, or a just plain kernel/driver bug. * It is unlikely to be a problem with the dump program or any portion of Amanda. Those all run in normal user space and usually with minimal special privileges. Probably the first few things I'd try are reseating everything that moves and checking all the DIP switches and jumpers. Twice. Then once more. Then I'd try a few dummy dumps (are you using dump or GNU tar?) along these lines (adjust as needed for your OS): dump 0f - /some/file/system /dev/null dump 9f - /some/file/system /dev/null If you have maxdumps set greater than one, you might try two (or more) of these at the same time to add even more contention. You might also try some large (dump image sized) ftp transfers from the client to /dev/null on the server. Unless you happen to find a FreeBSD expert here (which is certainly likely), my guess is you'll need to go those mailing lists to get much more help with this. They might be able to tell you, for instance, how to get into the machine when it is hung and find out exactly what processes are running, what the kernel is doing, etc. Ryan Williams John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: server crashes
One thing on that server that I find kinda hard to understand is that at a different time of the day, every day, the whole server is dumped to a second hard drive with the same vendor dump program. I took out the -u option so it did not use /etc/dumpdates. I am more apt to believe that it is a driver problem with the ethernet card because I am having a problem on two other machines with that same nic. They are all 3c509 nics but the weird thing is that on the other ones when a backup is run, they just stop responding on that nic. If I try to ping out that nic it gives an error of ping: sendto: No buffer space available I have been searching places like google and it seems like this may be linked to a bad drive because I found people that had the same driver and the same error. I dont know why that one would be freezing instead of just breaking that nic card though. - Original Message - From: "John R. Jackson" [EMAIL PROTECTED] To: "Ryan Williams" [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Monday, February 05, 2001 11:42 PM Subject: Re: server crashes ... Each time amdump runs on the server, one of the clients (a freebsd 4.0 box) completely hangs without an error in the /var/log/messages. I have not found any logs to tell me what broke when I ran a backup. Does anyone have an idea about what is wrong or what I should check? This is all guesswork because I don't run FreeBSD, but that's never stopped me from shooting off my E-mouth before :-): * It could be any number of hardware problems, including the disk being backed up, the cable, the controller, seating of any of the things that move, bad termination, bad option switch settings, speed mismatches (SCSI-2 on a SCSI-1 bus), bad firmware, bad DMA control to/from memory, bad memory, etc. It could also be any of the above with the network interface rather than the disk. * It could be a kernel problem dealing with a hardware problem, or a just plain kernel/driver bug. * It is unlikely to be a problem with the dump program or any portion of Amanda. Those all run in normal user space and usually with minimal special privileges. Probably the first few things I'd try are reseating everything that moves and checking all the DIP switches and jumpers. Twice. Then once more. Then I'd try a few dummy dumps (are you using dump or GNU tar?) along these lines (adjust as needed for your OS): dump 0f - /some/file/system /dev/null dump 9f - /some/file/system /dev/null If you have maxdumps set greater than one, you might try two (or more) of these at the same time to add even more contention. You might also try some large (dump image sized) ftp transfers from the client to /dev/null on the server. Unless you happen to find a FreeBSD expert here (which is certainly likely), my guess is you'll need to go those mailing lists to get much more help with this. They might be able to tell you, for instance, how to get into the machine when it is hung and find out exactly what processes are running, what the kernel is doing, etc. Ryan Williams John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: gzip
1. I have all of my gzips set to fast instead of best but whenever amdump is running there will be a gzip --fast and gzip --best for every file that is in my holding disk. What are the reasons behind this? The --best one is doing the index files, not the data stream. 2. quoting a colocation facilitys website: "We use bzip2 instead of gzip for data compression. ... This comes up here about once a month :-). There was a lengthy discussion last November. Quoting Alexandre Oliva: ... people who tried to use bzip2 for backup compression ended up finding out it was just too slow. And then Jonathan F. Dill after some (non-Amanda) timing tests: In summary, bzip2 gave me 3.84% more compression at a cost of a more than fourfold increase in the time that it took to run the compression. Even so, there is something called the "FILTER API" that should allow arbritrary programs to be inserted in the data stream (compression, encryption, random number :-) and this would be the logical place to put this effort. Ryan Williams John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: Amanda Client on FreeBSD
First off, I just want to start this out saying that I am not an expert at this by far but I have read the chapter from backup central about 5 times ... As far as I'm concerned, that makes you an "expert" :-). In freebsd you must add amanda to the group operators. ... That depends on whether you are using dump or GNU tar and what group has read access to the raw disk devices. GNU tar doesn't need special group membership because it runs under a setuid-root wrapper. For dump, you either need to put Amanda in the group that owns the devices, or change the group of the devices to something Amanda is a member of (possibly a brand new Amanda only group). You don't use the directory's when telling it what to backup ... I prefer to use the logical (mount point) names rather than the disk names. I've moved data around too often in the past and prefer the extra level of indirection. But this is personal preference. Amanda can handle either. For GNU tar it will convert a disk name to the mount point. For dump it will convert a mount point to the disk (assuming, in either case, your /etc/fstab or the equivalent is correct). John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
