Re: Amrecover
Hi all tks to my list friends to help-me with amanda :) the amanda working fine !!! But, i have one question the amanda can make backup in windows servers wirh samba ok? what is the differ in make backupcin one server running samba mounting this server in mnt/nameofserver and make backup this partition on put in disklist the name of the server and your share? tks Marcelo
Re: amandaidx acess still not allowed (bilingual)
Hi again!! The 71 bytes in the file is more than the 52 I would expect with the above context. That means there is something else in .amandahosts, maybe some other hosts. That would be correct. But as you clearly have a problem with the .amandahosts, it would be easier to post it, so that others can point out the errors in it. Maybe it's a typing error, which you fail to see (I've been bitten by that kind of errors many times!). What is the output of: $ cat ~amanda/.amandahosts executed on the server (not the client!) $ cat ~amanda/.amandahosts irixoa06.des.udc.es amanda irixoa06.des.udc.es root And did you configure and build it as the unpriviledged user (amanda?), and become root to install it? Please post the results of an 'amcheck nameofconfig' executed by the user who built amanda. $ amcheck Diaria Amanda Tape Server Host Check - Holding disk /dumps/amanda: 226936 KB disk space available, that's plenty amcheck-server: slot 1: date 20040311 label Diaria1 (exact label match) NOTE: skipping tape-writable test Tape Diaria1 label ok Server check took 0.758 seconds Amanda Backup Client Hosts Check Client check: 1 host checked in 0.133 seconds, 0 problems found (brought to you by Amanda 2.4.4p2) The other bytes was there because before i had the server as other client. Now I erase this entry amada_serv amanda, but the message is the same, remember: $amrecover Diaria AMRECOVER Version 2.4.4p2. Contacting server on irixoa06 ... 220 irixoa06 AMANDA index server (2.4.4p2) ready: 500 Access not allowed: [access as amanda not allowed from [EMAIL PROTECTED] amandahostsauth failed Thanks for your help!! In spanish: Hola otra vez!! The 71 bytes in the file is more than the 52 I would expect with the above context. That means there is something else in .amandahosts, maybe some other hosts. That would be correct. But as you clearly have a problem with the .amandahosts, it would be easier to post it, so that others can point out the errors in it. Maybe it's a typing error, which you fail to see (I've been bitten by that kind of errors many times!). What is the output of: $ cat ~amanda/.amandahosts executed on the server (not the client!) $ cat ~amanda/.amandahosts irixoa06.des.udc.es amanda irixoa06.des.udc.es root And did you configure and build it as the unpriviledged user (amanda?), and become root to install it? Please post the results of an 'amcheck nameofconfig' executed by the user who built amanda. $ amcheck Diaria Amanda Tape Server Host Check - Holding disk /dumps/amanda: 226936 KB disk space available, that's plenty amcheck-server: slot 1: date 20040311 label Diaria1 (exact label match) NOTE: skipping tape-writable test Tape Diaria1 label ok Server check took 0.758 seconds Amanda Backup Client Hosts Check Client check: 1 host checked in 0.133 seconds, 0 problems found (brought to you by Amanda 2.4.4p2) Los otros bytes estaban ahí porque antes tenía al servidor como otro cliente. Ahora borré esa entrada amanda_ser amanda, pero el mensaje es el mismo, recordar: $amrecover Diaria AMRECOVER Version 2.4.4p2. Contacting server on irixoa06 ... 220 irixoa06 AMANDA index server (2.4.4p2) ready: 500 Access not allowed: [access as amanda not allowed from [EMAIL PROTECTED] amandahostsauth failed Gracias por vuestra ayuda!! __ Correo Yahoo! - 6 MB, antivirus y antispam ¡gratis! Regístrate ya - http://correo.yahoo.es
Re: Amrecover
On Monday 31 May 2004 09:14, Marcelo Leão Caffaro wrote: Hi all tks to my list friends to help-me with amanda :) the amanda working fine !!! But, i have one question the amanda can make backup in windows servers wirh samba ok? what is the differ in make backupcin one server running samba mounting this server in mnt/nameofserver and make backup this partition on put in disklist the name of the server and your share? The biggest problem is that samba, like almost any windows/ms compatible app, does not handle the atime on the file, so amanda gets garbage in that bit of the files descriptor. So doing backups with samba as the transport agent tends to do fulls 99% of the time when it means to do an incremental. This is a windows/ms problem, not an amanda problem. tks Marcelo -- 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.
Re: amandaidx acess still not allowed (bilingual)
On Monday 31 May 2004 10:29, Pablo Quintía Vidal wrote: Hi again!! The 71 bytes in the file is more than the 52 I would expect with the above context. That means there is something else in .amandahosts, maybe some other hosts. That would be correct. But as you clearly have a problem with the .amandahosts, it would be easier to post it, so that others can point out the errors in it. Maybe it's a typing error, which you fail to see (I've been bitten by that kind of errors many times!). What is the output of: $ cat ~amanda/.amandahosts executed on the server (not the client!) $ cat ~amanda/.amandahosts irixoa06.des.udc.es amanda irixoa06.des.udc.es root And did you configure and build it as the unpriviledged user (amanda?), and become root to install it? Please post the results of an 'amcheck nameofconfig' executed by the user who built amanda. $ amcheck Diaria Amanda Tape Server Host Check - Holding disk /dumps/amanda: 226936 KB disk space available, that's plenty amcheck-server: slot 1: date 20040311 label Diaria1 (exact label match) NOTE: skipping tape-writable test Tape Diaria1 label ok Server check took 0.758 seconds Amanda Backup Client Hosts Check Client check: 1 host checked in 0.133 seconds, 0 problems found (brought to you by Amanda 2.4.4p2) The other bytes was there because before i had the server as other client. Now I erase this entry amada_serv amanda, but the message is the same, remember: $amrecover Diaria AMRECOVER Version 2.4.4p2. Contacting server on irixoa06 ... 220 irixoa06 AMANDA index server (2.4.4p2) ready: 500 Access not allowed: [access as amanda not allowed from [EMAIL PROTECTED] amandahostsauth failed Thanks for your help!! You still have something fubared in the install. As root, from within the src dir, do a chown -R user:group * where user:group is the amanda-user-name:and-group-amanda-is-a-member-of, s/b disk or backup, bin maybe. Then grab a file manager as root, like mc, and go find the stuff already installed (executables, not your configs!) and nuke it. Then as root, do another make install. In spanish: Hola otra vez!! The 71 bytes in the file is more than the 52 I would expect with the above context. That means there is something else in .amandahosts, maybe some other hosts. That would be correct. But as you clearly have a problem with the .amandahosts, it would be easier to post it, so that others can point out the errors in it. Maybe it's a typing error, which you fail to see (I've been bitten by that kind of errors many times!). What is the output of: $ cat ~amanda/.amandahosts executed on the server (not the client!) $ cat ~amanda/.amandahosts irixoa06.des.udc.es amanda irixoa06.des.udc.es root And did you configure and build it as the unpriviledged user (amanda?), and become root to install it? Please post the results of an 'amcheck nameofconfig' executed by the user who built amanda. $ amcheck Diaria Amanda Tape Server Host Check - Holding disk /dumps/amanda: 226936 KB disk space available, that's plenty amcheck-server: slot 1: date 20040311 label Diaria1 (exact label match) NOTE: skipping tape-writable test Tape Diaria1 label ok Server check took 0.758 seconds Amanda Backup Client Hosts Check Client check: 1 host checked in 0.133 seconds, 0 problems found (brought to you by Amanda 2.4.4p2) Los otros bytes estaban ahí porque antes tenía al servidor como otro cliente. Ahora borré esa entrada amanda_ser amanda, pero el mensaje es el mismo, recordar: $amrecover Diaria AMRECOVER Version 2.4.4p2. Contacting server on irixoa06 ... 220 irixoa06 AMANDA index server (2.4.4p2) ready: 500 Access not allowed: [access as amanda not allowed from [EMAIL PROTECTED] amandahostsauth failed Gracias por vuestra ayuda!! __ Correo Yahoo! - 6 MB, antivirus y antispam ¡gratis! Regístrate ya - http://correo.yahoo.es -- 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.
Re: Amrecover
Hi, i need reinstall my linux and now i have this problem, anyone can help-me? sendsize: debug 1 pid 3717 ruid 502 euid 502: start at Mon May 31 14:08:09 2004 sendsize: version 2.4.4p2 sendsize[3879]: time 6.964: calculating for amname '/opt', dirname '/opt', spindle -1 sendsize[3879]: time 6.964: getting size via dump for /opt level 0 sendsize[3717]: time 7.005: waiting for any estimate child: 1 running sendsize[3879]: time 13.954: calculating for device '/opt' with '' sendsize[3879]: time 13.954: running /sbin/dump 0Ssf 1048576 - /opt sendsize[3879]: time 13.959: running /usr/local/libexec/killpgrp sendsize[3879]: time 13.964: DUMP: Cannot open /dev/ide/host0/bus0/target0/lun0/part1 sendsize[3879]: time 13.965: DUMP: The ENTIRE dump is aborted. sendsize[3879]: time 13.966: . sendsize[3879]: estimate time for /opt level 0: 0.011 sendsize[3879]: no size line match in /sbin/dump output for /opt sendsize[3879]: . sendsize[3879]: estimate size for /opt level 0: -1 KB sendsize[3879]: time 13.966: asking killpgrp to terminate sendsize[3879]: time 14.968: done with amname '/opt', dirname '/opt', spindle -1 sendsize[3717]: time 14.968: child 3879 terminated normally sendsize: time 14.968: pid 3717 finish time Mon May 31 14:08:24 2004
switching between drives
I have one external DLT tape drive (40/80 GB) at my backup server, but I have to backup 130 GB. I have another internal DLT tape drive (40/80 GB). Could I add another DLT drive (40/80 GB) and tell this to amanda : When the first tape be full, continue the backup into another tape drive ? Instead I change the tape manually, amanda change the tape drive for me ... Or I have to add this tape drive into an autoloader ? Regards. InfraNet Tecnologia Fábio M. A. Cunha (55 11) 5542-0941 ramal 22 (55 11) 9603-6377 www.infranetsp.com.br
Re: switching between drives
have 2 seperate amanda configs and run some of the DLE's on one config to one drive and the rest on the other config on the other drive that way you can have the whole lot backup to both drives on its own. I do this and it works great - Original Message - From: FXbio MendonXa Albuquerque Cunha [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, May 31, 2004 10:23 PM Subject: switching between drives I have one external DLT tape drive (40/80 GB) at my backup server, but I have to backup 130 GB. I have another internal DLT tape drive (40/80 GB). Could I add another DLT drive (40/80 GB) and tell this to amanda : When the first tape be full, continue the backup into another tape drive ? Instead I change the tape manually, amanda change the tape drive for me ... Or I have to add this tape drive into an autoloader ? Regards. InfraNet Tecnologia Fábio M. A. Cunha (55 11) 5542-0941 ramal 22 (55 11) 9603-6377 www.infranetsp.com.br
Re: suggestions for RH amanda installation
On Sat, May 29, 2004 at 02:07:22PM -0400, Jon LaBadie wrote:
I see gcc 2.96 is already installed as is a libreadline (don't
hold me to it, but I think 4.3). Stupidly I forgot to check the
tar version. Any thoughts on the compiler and readline versions?
I compiled Amanda with whatever was already on each host. On the
subset of boxes that I just checked, including the server, that's
2.95.{2,4}. (That's on a mixture of x86/Linux, x86/FreeBSD and
Sparc/Solaris -- varying O/S versions). I haven't seen any
problems as a result.
Might installing newer compiler and libs upset the vendor's app?
I must avoid that at all costs.
You could always build Amanda on some other box, with whatever
versions of stuff you like. If you build it statically, it
shouldn't have any library dependencies at all on the machines it
runs on. To be safe, make sure to use a kernel of the right
vintage, so that configure can make the right decisions.
BTW I'm aware of LT's rant about dump not being safe.
Well, he'd know... But then, he was talking about 2.4 and 2.6
kernels, IIR. If 7.3 has a 2.2 kernel, you might be ok.
After compiling the server version of amanda, is it feasible/easy,
to also compile just the client version on the server and build
an rpm to install on the other 4 workstations?
I haven't tried this, but I don't see why not. From what I've
read here, the problem with RPMed Amanda is that the RPM builder
has to make a lot of configuration choices you might not like.
If you build the RPMs yourself, that's obviously not a problem.
So they are talking about periodically copying a day's backup
to a tape device, avoiding the need to do a separate archival
backup. Silly persons :)) Considering I would be doing normal
amanda type scheduling and using virtual tapes on the big disk,
any ideas on an archival scheme that would fit amanda's and the
client's view of the world?
Our main Amanda configuration backs up to file: pseudo-tapes, and
runs 5 days a week. Another configuration with record no does
all level 0's to tape on Friday nights; the tapecycle contains
about two months' worth of tapes. A third configuration runs on
the first Friday of every second month. It's just like the
second, but the tape-label regexp is different, and the tapes are
never reused, i.e. the tapecycle is huge.
The idea is that the second configuration is offsite backup, for
disaster recovery, and the third is a permanent historical
archive. Only one of these configurations runs on any given
night. I could have accomplished both of these goals with one
fewer configurations and judicious use of no-reuse once every
two months, but that would have been more susceptible to operator
error.
--
| | /\
|-_|/ Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED]
| | /
It must be said that they would have sounded better if the singer
wouldn't throw his fellow band members to the ground and toss the
drum kit around during songs.
- Patrick Lenneau
disk offline error
Hi all, I have a very functional amanda 2.4.3 LAN backup system that I'm having one problem with: I can't seem to back up any partitions, only directories and files. If I use disklist specs like this node1 /home standard I get a proper backup, but if I use node1 /dev/sda9 standard I get an error saying that sda9 is offline. But it isn't, so I figured there must be a permissions problem, but amanda is in the disk group, and that device node is in the disk group as well, with proper rw perms. I also tried node1 /dev/scsi/host1/bus0/target1/lun0/part9 standard also to no good end. Any ideas/clues? How can I verify the permissions are working on the node1 side beyond checking with ls -la? Thanks!
Re: disk offline error
/dev/sda9 is NOT a mount point, its a descriptor only and will probably fail forever. now, if that disk is mounted someplace, as in /mnt/sda9 on the machine whose alias is node1, and it is mounted when amdump runs, it should work like a champ. Ok, what I'm experiencing lends that a lot of credence, but what sent me off in this direction was (from the amanda distribution, example disklist entries) # Dump Joe's NetBSD machine, with the mounted MS-DOS partition dumped # using tar. #joespc wd0a comp-root #joespc wd0e comp-user #joespc /msdos comp-user-tar which seems to imply that it's possible to back up unmounted partitions, and that would be really great! I've always been under the impression that this was amanda-possible somehow, but never have been able to make it happen. Seems like this would be the way to back up a partition regardless of formatting (like an HFS+ or NT part, which is really what I'm after).
