Making backup to HDD only
Hello, I need to make backup on HDD only, because we don't have good tape yet. Is it possible and is some specail configuration required? Thanks Tomas Toth - serverside technologies, PHP3 SQL developer WWL Internet Praha s.r.o. e-mail. [EMAIL PROTECTED] icq: 46410328 Soukenicka 23, Praha 1, 110 00, Czech Republic tel./fax +420/2/24811505, gsm-gate: +420/604/684882 http://wwl.cz
Re: Making backup to HDD only
On Nov 27, 2000, "Tomas Toth" [EMAIL PROTECTED] wrote:
I need to make backup on HDD only, because we don't have good tape yet.
Is it possible and is some specail configuration required?
Basically, you have to set reserve 0, and configure /dev/no/tape (or
any other non-existing device) as the tape device. But don't use
/dev/null; this will discard your backups, if you're running 2.4.2.
You'll have to clean up the holding disk every now and then.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicampoliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist*Please* write to mailing lists, not to me
Re: Making backup to HDD only
You can kind of do it. Basically: Set the reserve parameter very low: reserve 0 And set the tape device to /dev/haha (unless you actually have a device called "/dev/haha"). You'll need to clear the backups manually when you want to get rid of them though...given that AMANDA names the directories with the dates, this shouldn't be too hard to do in PERL (or some other language with regular expressions). DL
Re: GNU tar estimates for vfat filesystems (Was: How do I checklevel 1 sizes?)
My suspicion is that GNU tar, which I use in the version 1.12, somehow cannot compute incrementals right, for filesystems of vfat type that are mounted the way I described above...(?) Even RedHat have a later version of GNU tar than 1.1.2 and (honestly) they're not known to release the latest versions of programs. Upgrade tar to at least (GNU tar) 1.13.17; the ones below this are likely to cause all sorts of weird problems. I'm using 1.13.17 and have the same problem: incrementals on vfat just don't work, they're effectively the same as full backups. tar seems to think that every file has been modified since the last backup. Searches elsewhere suggest that it stems from a rewrite of the kernel vfat support between kernels 2.10 and 2.11, but I couldn't find a solution mentioned anywhere (*). It's very frustrating. If anyone else has an idea what to do I'd be ecstatic: this added hours to my daily incrementals until I just gave up on backing up Windows. Conrad * If I understand correctly (and there's no guarantee that I do), the vfat change was to ensure that a file on a vfat FS would have the same inode number for the duration of a single mount; inodes need to be constructed in some manner on vfat because it doesn't actually have real inodes, and the previous mechanism meant that a file's inode wouldn't be constant (for example a rename would change it; this caused much gnashing of teeth among one crowd of people). This new mechanism means inodes are fixed for the duration of a mount, but if you umount and remount then you have no guarantee of continuity; this is now causing gnashing of teeth amoung another crowd. Since tar --listed-incremental seems to record inodes, it gets very confused if the machine umounts and mounts a vfat system between backups (as would inevitably be the case if you rebooted for example).
Re: How long does tapetype run?
Hi, now tapetype runs nearly 7 days with my OnStream ADR 50. Are there any estimates, how long it will take? My output is: wrote 675390 32 Kb blocks in 12320 seconds wrote 66600 32 Kb sections ...when it will take another 2 months, I will look for another backup software. ;-)) Greetings Olaf On 22 Nov 2000, at 10:19, Olaf Seidel wrote: Hi, I'm wondering about the time, how long tapetype runs. I used tapetype on an OnStream ADR50 and it runs 41 hours and 19 minutes. OK, the manual says, that the process could take hours or days. But which tests will come after the following output: wrote 67539 32 Kb blocks in 12320 seconds wrote 15400 32 Kb sections Thanks in advance... Greetings Olaf P.S.: I will post the output data to the group after tapetype is finished.
Re: amanda-2.4.2 (question: do I have to update all clients?)
The Amanda core team is pleased to announce the release of Amanda 2.4.2. It fixe a many bugs and have many new feature since amanda-2.4.1p1. Excellent! Question: If I update the host, do I also have to update the rest of them? I ask, because I have several OSs working together here, FreeBSD and RedHat Linux. --- Eric
Re: ADR-50
Hi Erik, I'm actually using tapetype with amanda. Tapetype isn't finished yet. So I don't know, if the ADR-50 will work with amanda. My former problems with the SCSI bus (See postings: "tapetype and ADR50") are solved. My Adaptec 29160 was too fast for the OnStream. I had to set up sync negotiation to "ASYNC". Another solution would be to set sync negotiation to 5 MB. Greetings Olaf On 27 Nov 2000, at 10:29, Erik W. Beese wrote: have you actually gotten the ADR-50 to work with amanda? if so how did you do it? Erik Beese
Problems with amanda and Red-Hat 7.0
Hi all,
I have installed the amanda rpms given with Red Hat 6.0.
After editing the configuration files I ran amcheck ... and I got the
following :
Amanda Tape Server Host Check
-
/storage/amanda: 8375172 KB disk space available, that's plenty.
NOTE: skipping tape-writable test.
Tape Daily1 label ok.
Index dir "/var/lib/amanda/DailySet1/index" doesn't exist or is not
writable.
Server check took 15.087 seconds.
Amanda Backup Client Hosts Check
WARNING: localhost: selfcheck request timed out. Host down?
Client check: 1 host checked in 30.001 seconds, 1 problem found.
(brought to you by Amanda 2.4.1p1)
The 3 configuration files in /etc/xinetd.d are as follows :
#xinetd.d file = amandad#
# default: off
#
# description: Part of the Amanda server package
service amanda
{
socket_type = dgram
protocol= udp
wait= yes
user= operator
group = disk
server = /usr/lib/amanda/amandad
disable = no
}
#xinetd.d file = amandaidx#
# default: off
#
# description: Part of the Amanda server package
service amandaidx
{
socket_type = stream
protocol= tcp
wait= yes
user= operator
group = disk
server = /usr/lib/amanda/amindexd
disable = no
}
#xinetd.d file = amidxtape#
# default: off
#
# description: Part of the amanda server package
#
service amidxtape
{
socket_type = stream
protocol= tcp
wait= no
user= operator
group = disk
server = /usr/lib/amanda/amidxtaped
disable = no
}
The permissions are :
-rw-r--r--1 operator disk 404 Nov 28 11:00 amanda
-rw-r--r--1 operator disk 412 Nov 28 10:42 amandaidx
-rw-r--r--1 operator disk 414 Nov 28 10:45 amidxtape
RedHat 7.0 runs amanda as the user "operator".
I tried to telnet to port 10080 (amandad port) but my connection was
refused (and it's the same with ports 10081 and 10082) ... which is the
reason why I guess selfcheck fails ... but I couldn't figure out why the
connection is refused given that there is no filter in the configuration
files!!
Has anybody had the same problems that I am having now???
Thanks in advance!!!
Bye, Antonino Casile
Re: ADR-50
Hi,
Olaf Seidel schrieb am 27. November 2000:
I'm actually using tapetype with amanda. Tapetype isn't finished
yet. So I don't know, if the ADR-50 will work with amanda. My
former problems with the SCSI bus (See postings: "tapetype and
ADR50") are solved. My Adaptec 29160 was too fast for the
OnStream. I had to set up sync negotiation to "ASYNC". Another
solution would be to set sync negotiation to 5 MB.
Hmm, with which Operating System? I am using it under NetBSD (current)
and it is working fine...:
ahc0: target 4 using 16bit transfers
ahc0: target 4 synchronous at 10.0MHz, offset = 0x8
Ciao, Hanno
--
| Hanno Wagner | Member of the HTML Writers Guild | Rince@IRC |
| Eine gewerbliche Nutzung meiner Email-Adressen ist nicht gestattet! |
| 74 a3 53 cc 0b 19 - we did it! |Generation @ |
#"Die ist doch hoechstens 4 minus"
# -- zu [EMAIL PROTECTED] ("Gib' mir 20 Minuten, Mann!")
Re: amanda-2.4.2 (question: do I have to update all clients?)
On Nov 27, 2000, Eric Wadsworth [EMAIL PROTECTED] wrote:
Question: If I update the host, do I also have to update the rest of them?
Nope. The Amanda protocol has remained unchanged since release 2.4.0.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicampoliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist*Please* write to mailing lists, not to me
Re: How long does tapetype run?
On Nov 27, 2000, "Olaf Seidel" [EMAIL PROTECTED] wrote:
now tapetype runs nearly 7 days with my OnStream ADR 50.
Are you using tapetype from Amanda 2.4.1p1? That was *slow*. 2.4.2
is orders of magnitude faster.
Another option is to search the FAQ-O-Matic.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicampoliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist*Please* write to mailing lists, not to me
Re: amanda-2.4.2 (question: do I have to update all clients?)
Question: If I update the host, do I also have to update the rest of them? No (I don't think so). As far as I recall, everything past 2.4.0b4 is compatible between client and server. I think I even had a couple of clients I forgot to update for several weeks when I went to 2.4.2 and they were perfectly happy. Of course, they know better than to mess with me :-). --- Eric John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Dump question
Hi, Should a 900MB dump over a 100Mbps network take about 10-12 hours to complete? The network load is light and useage on the host and client is low. I must be missing something -- this seems way too slow. Any suggestions? Shane T. Ferguson
Re: Dump question
Should a 900MB dump over a 100Mbps network take about 10-12 hours to complete? ... This could be caused by several things, such as disk contention, disk fragmentation, disk bad blocks, SCSI problems, etc. However, whenever I see the term "100 Mbps" (I assume you mean EtherNet) and slow performance, I instinctively start checking for duplex problems, and 99% of the time this turns out to be the problem. Solaris, in particular, is notorious for not auto-negotiating it properly for their hme interface, resulting in a speed drop of several orders of magnitude. The magic /etc/system incantations have been posted here several times, or if you can't find them, E-mail me offline. Shane T. Ferguson John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: amstatus reports 190% complete??
Eric Wadsworth [EMAIL PROTECTED] writes: Here's a line from my amstatus results: xxx:/usr/abc_share 0 210835k dumping 406944k (193.02%) What does this mean? I thought 100% was sort of a maximum... --- Eric It just means there were more data to backup than amanda expected. Or that the data didn't compress as much as expected. /Jens -- Jens Bech Madsen Computerrummet, TSGDK
amanda install
Hello all! I have numerous questions about amanda all leading hopefully towards making it work. The short story is that now 'amcheck' runs w/o errors but when I issue "amdump daily" it appears as if nothing happens and I get the prompt back immediately. 'daily' is the name of my config. amlabel is happy with my EXB-8500 as /dev/nst0. The progression of events was as follows: I installed amanda-2.4.2p1 as root on my TurboLinux 6.0 (WS) workstation (aka my server at home) and had a really difficult time getting anywhere with it failing at the amcheck step. I created, recreated, moved and chmod'd directories and files trying to make sense out of what appears to be a mixture of at least three standards for file locations in the README, INSTALL, /amanda-2.4.2/eamaple/amanda.conf file and the chapter from W. Curtis Preston's book "Unix Backup and Recovery" as posted at www.amanda.org. I recognize this as a common 'Linux' problem so I did the best that I could to resolve by couth and sleuth. At some point noticed that there is an amanda-2.4.2 version and it appeared as though it is no longer beta. So taking into concideration the comments about running './configure' and 'make' as user amanda and then running 'make install' as root (also found at www.amanda.org in the FAQ section), I did just that after cleaning out as much garbage from the previous install as I knew where it lived (read: the source directory and directories that I had created). Amcheck still failed and still showed brought to you by Amanda 2.4.1p1 - is this a key indicator of my problem? I fianlly was able to get amcheck to pass off my install as good. :) What follows is what I had to do to get amcheck to run successfully. I had to manually create and assign permissions for numerous files and directories including, and I hope limited to (asuming I was thorough in my note taking): /etc/amandates file, /etc/amanda/daily/amanda.conf and disklist (where amanda.conf was copied from /amanda-2.4.1p1/examples and edited, daily is the name of my configuration and disklist just includes my server's "/" dir at present), /var/amanda/curinfo and /index directories, /usr/local/var/amanda/gnutar-lists file, /home/amanda/.amandahosts, /etc/amanda/daily/tapelist file, added my user amanda to 'disks' group to access /dev/nst0 and /dev/hd*, ran /amanda-2.4.2/client-src/patch-system script to modify /etc/services and inted.conf files, added PATH=/usr/sbin:$PATH to /home/amanda/.bashrc, created /dumps/amanda, usr/lib/amanda and copied to it /usr/local/sbin/amgetconf as getconf to make amcheck happy. Now amcheck is happy. When I run "amdump daily" the prompt returns immediately and nothing further happens, including no messages or mail. Any ideas what is wrong here? And you are not allowed to select 'Randy' as the answer to that question. grin. Randy Cordell. ps: tar cvf /dev/st0 /* works fine. __ Do You Yahoo!? Yahoo! Shopping - Thousands of Stores. Millions of Products. http://shopping.yahoo.com/
questions about amsdump/ufsrestore
Hi:
I've installed amanda 2.4.1 on a Sun Ultra 30 with an Exabyte 8500
tape drive. I'm in the tryout/testing phase right now. Eventually,
we hope to run amanda on a dedicated Sun server with a heftier tape library.
O.K., my question:
I'm dumping two filesystems on my tape server, which is also acting
as my backup client during the testing phase. Here is my disklist
definition (server/client is emerald):
# emerald
#
emerald /usr/samba nocomp-high
emerald /varnocomp-high
In amanda.conf, my dumptype definition for nocomp-high looks like this:
define dumptype nocomp-high {
comp-high
index yes
comment "very important partitions on slow machines"
compress none
program "DUMP"
}
I'm assuming that the "program "DUMP"" parameter will utilize the
local dump utility, which is "ufsdump". If this is so, shouldn't
I be able to use "dd" to access tape contents, and pipe it to
"ufsrestore"? I've tried this:
dd if=/dev/rmt/0mn bs=64k skip=1 | ufsrestore -tv
but I get this error messages:
dd if=/dev/rmt/0mn bs=64k skip=1 | ufsrestore -tv
Verify volume and initialize maps
/dev/rmt/0: Device busy
# 0+0 records in
0+0 records out
If I don't use "bs=64k" with "dd", I get the error message:
Volume is not in dump format
Also, "ufsrestore" insists on some parameters, hence the "-tv".
Is anyone else trying to use native dump on a Sun machine, and successfully
restoring using Sun's ufsrestore?
(I tested amrecover earlier and it worked fine - at that time, though,
I didn't have that "program "DUMP"" line in my dumptype definition. I'll
test amrecover again to make sure my baseline hasn't moved.)
Lisa
--
Lisa M. Becktold - [EMAIL PROTECTED], (410) 293-6480
United States Naval Academy - CADIG
590 Holloway Road, Rickover Hall, Annapolis, MD 21402-5000
Re: amrecover problems
What's in amidxtaped.debug on amanda??? Nothing that tells me anything, that's the problem. But it might mean something to someone else. :-) I currently have a restore going, so as soon as it finishes, I'll rerun it and let you know. OK. One question I have though is, should I have to manually load each tape into the drive (by manually, I mean using 'amtapee config slot X') or should I just be able to answer 'Y' when it asks me "Load next tape now" and expect amanda to find the correct tape in the changer library? Loading "by hand" is, unfortunately, the current technique. Amidxtaped (what amrecover uses to process the tapes) uses amrestore to process the tape. Amrestore doesn't know about changers or anything else in an Amanda configuration (it's meant to be a stand alone utility). And amidxtaped was never taught about them, either. There is a discussion going on right now in amanda-hackers about the changes needed to get this to behave better. Feel free to join in :-). Paul John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: questions about amsdump/ufsrestore
Hi, John:
Thanks very much for your reply!
O.K., I tried that "dd" command, and my output looks a little more
civilized (no "drive busy" messages now):
# dd if=/dev/rmt/0mn bs=32k skip=1 | ufsrestore -tvbf 2 -
Verify volume and initialize maps
0+0 records in
0+0 records out
Volume is not in dump format
Do you think there may be a problem with the way I did the dump?
I used this command:
amsdump Daily
Thanks!
Lisa
To: Lisa Becktold {CADIG STAFF} [EMAIL PROTECTED]
cc: [EMAIL PROTECTED]
Subject: Re: questions about amsdump/ufsrestore
Date: Mon, 27 Nov 2000 16:42:19 -0500
From: "John R. Jackson" [EMAIL PROTECTED]
I'm assuming that the "program "DUMP"" parameter will utilize the
local dump utility, which is "ufsdump". ...
It will use the local dump utility associated with the file system type
as determined at run time. For instance, it (automatically) flips around
between ufsdump and vxdump on my Solaris systems.
If this is so, shouldn't
I be able to use "dd" to access tape contents, and pipe it to
"ufsrestore"? I've tried this:
dd if=/dev/rmt/0mn bs=64k skip=1 | ufsrestore -tv
You **must** use 32k on the dd. That's the block size Amanda uses and
anything is is not going to work right.
The main problem, though, is that you forgot a parameter on ufsrestore,
and it's trying to read the tape at the same time dd is. Do it this way:
dd if=/dev/rmt/0mn bs=32k skip=1 | ufsrestore -tvbf 2 -
It's the 'f' and '-' flag and argument that tell ufsrestore to read
from stdin. The 'b' and '2' flag and argument tell it to read in small
chunks (1 KByte), which is needed by some restore programs when dealing
with piped input.
Lisa
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
--
Lisa M. Becktold - [EMAIL PROTECTED], (410) 293-6480
United States Naval Academy - CADIG
590 Holloway Road, Rickover Hall, Annapolis, MD 21402-5000
Re: questions about amsdump/ufsrestore
O.K., I tried that "dd" command, and my output looks a little more civilized (no "drive busy" messages now): ... Yes, much better. # dd if=/dev/rmt/0mn bs=32k skip=1 | ufsrestore -tvbf 2 - Verify volume and initialize maps 0+0 records in 0+0 records out Where is the tape positioned? There is an Amanda label on the front of the tape before the first backup image. So you need to skip over that first with "mt fsf" if the tape is rewound. You should be able to use: su amanda-user -c "amadmin Daily find client-host client-fs" to find out what tape and what file on that tape contain the backup image for filesystem "client-fs" on "client-host". Take a look at the amadmin man page though -- both client-host and client-fs are forms of regular expressions. Also, are you just doing some low level testing? In other words, is there are reason you're not using amrestore or amrecover? Lisa John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: Completely Stuck :-(
I'm hoping someone can shed some light on this one, basically I'm convinced amandad never runs from inetd, and I"ve spent days on this so far :-( Then it's definitly time to ask :-). and inetd has (on one line!): amanda dgram udp wait amanda /opt/local/libexec/amandad amandad ... If I run the above manually (as root or amanda), the /tmp/amanda/ directory is created, as well as the debug file. So I delete that, kill-HUP inetd just to be safe, and then run amcheck. Nov 24 12:00:27 hostname inetd[168]: [ID 858011 daemon.warning] /opt/local/libexec/amandad: Hangup This says, as you sort of suspected, that inetd is not able to run amandad for some reason. It is, however listening on the port and so forth, so that part's configured properly. BTW, after it fails like this, inetd will disable the service (that's what it means by "service terminated") for 10 minutes. If you continue to do testing before it re-enables it, nobody will be listening on the port, which will no doubt add to the confusion. Sending inetd a HUP will re-enable everything right away. I know you said the above inetd.conf entry was on one line, but could you confirm absolutely that that trailing "amandad" is really there and is on the same line? That's been a typical problem in the past. When you ran amandad as user amanda, did you give it the full path as in the inetd.conf line? Something like: su amanda -c /opt/local/libexec/amandad And I assume it sat there for 30 seconds then dropped away? If none of this sheds any light, then next entry out of the bag 'o tricks is to write a little shell script like this: #!/bin/ksh exec /tmp/amandad.out.$$ 21 print "$(date): starting amandad" /opt/local/libexec/amandad print "$(date): amandad done: status is $?" exit 0 Put it in (e.g.) /tmp (it's just for testing, not for production), chmod +x it, then change the inetd.conf line to point at the script instead of directly at amandad. Make sure you leave the trailing "amandad" on the line. The script will run amandad but redirect stdout/stderr to another /tmp file. See if they have anything interesting to say. If the script at least tries to run (e.g. you get the "starting amandad" message) but does not give any more insight, change the call to amandad in the script to: /bin/truss -aelv all /opt/local/libexec/amandad which will dump loads of stuff to stderr. Hopefully one of the last things you see it try to do will point the way to the real problem. Also I'm not 100% as to what should be going on with .amandahosts, at present I have it in ~amanda, containing 'hostname amanda' and this seems OK. That's correct (I assume by "hostname" you mean the name of your server), with the addition that it should be owned by amanda and mode 0600 or 0400. - John John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: questions about amsdump/ufsrestore
Hi, John: Where is the tape positioned? There is an Amanda label on the front of the tape before the first backup image. So you need to skip over that first with "mt fsf" if the tape is rewound. Yup, that worked! Here's output: # mt rewind # mt fsf # dd if=/dev/rmt/0mn bs=32k skip=1 | ufsrestore -tvbf 2 - Verify volume and initialize maps Extract directories from tape Initialize symbol table. Dump date: Mon Nov 27 15:24:45 2000 Dumped from: Mon Nov 20 14:57:37 2000 Level 1 dump of /usr/samba on emerald:/dev/dsk/c0t12d0s3 Label: none dir 2 . dir 423936 ./var dir 11789 ./var/locks leaf 11793 ./var/locks/browse.dat leaf 11792 ./var/locks/STATUS..LCK leaf423938 ./var/log.smb leaf423950 ./var/log.tspc39ab 18+0 records in 18+0 records out But why do you have to use both "mt fsf" and "skip=1"? Does "mt fsf" skip the volume label? And then "skip=1" skips over the first block, which contains the amanda file header? Guess I've been conditioned by years of using just ufsdump/ufsrestore Also, are you just doing some low level testing? In other words, is there are reason you're not using amrestore or amrecover? Kind of a worst-case scenariowe want to make sure we can use low-level, standard Unix utilities to restore files/directories. With that dd/ufsrestore combo, it looks like we can access files on an amanda tape using an Exabyte attached to another Unix server - and that Unix server doesn't need to run amanda utilities. You should be able to use: su amanda-user -c "amadmin Daily find client-host client-fs" to find out what tape and what file on that tape contain the backup image for filesystem "client-fs" on "client-host". O.K., great, that worked, too. As amanda user, I ran that command and got this output: amadmin Daily find emerald /usr/samba Scanning /disk6/amanda... date hostdisk lv tape or file file status 2000-11-20 emerald /usr/samba 0 DailySet101 1 OK 2000-11-24 emerald /usr/samba 1 DailySet103 1 OK 2000-11-27 emerald /usr/samba 1 DailySet104 1 OK I would use this data to track down a tape for a backup of /usr/samba, right? Thanks for all the info and clarifications! Lisa -- Lisa M. Becktold - [EMAIL PROTECTED], (410) 293-6480 United States Naval Academy - CADIG 590 Holloway Road, Rickover Hall, Annapolis, MD 21402-5000
Re: questions about amsdump/ufsrestore
Yup, that worked! Here's output: ... Looks good. But why do you have to use both "mt fsf" and "skip=1"? Does "mt fsf" skip the volume label? And then "skip=1" skips over the first block, which contains the amanda file header? ... That's correct. You would (might) also use fsf to get to the second, third, etc, image on the tape. Typically you'll back up dozens or hundreds of file systems on a single tape, and each one is in its own (tape) file. Kind of a worst-case scenariowe want to make sure we can use low-level, standard Unix utilities to restore files/directories. ... Ahh, I see. You're one of those silly plan ahead types :-). With that dd/ufsrestore combo, it looks like we can access files on an amanda tape using an Exabyte attached to another Unix server - and that Unix server doesn't need to run amanda utilities. Absolutely. One of the greatest things about Amanda. If I were you, I'd go ahead and install the Amanda software (it's pretty small) on your other Unix server just so you can have amrestore if needed. As you've found out, dd works fine, but why have to remember that at 3AM if you don't have to? :-) FYI, I have one or more alternate server hosts (actually, they are primaries for their own configurations) for each of my primary hosts. At the end of each amdump run, I rdist most of the config information (it's not all the big) to the alternate host so if the primary goes down, I can still use the Amanda tools on the alternate and even have the databases to do searches just like it was the primary. I also take tapes from the primary to the alternates each week and make sure they can be read with amverify. This makes it more likely that the drives are not drifting too far out of alignment w.r.t. each other. date hostdisk lv tape or file file status 2000-11-20 emerald /usr/samba 0 DailySet101 1 OK 2000-11-24 emerald /usr/samba 1 DailySet103 1 OK 2000-11-27 emerald /usr/samba 1 DailySet104 1 OK I would use this data to track down a tape for a backup of /usr/samba, right? Not only the tape but the file on the tape. In the above, it's always the first file, 1, but here's an example from my site: date host disk lv tape or file file status 2000-10-18 gandalf.cc.purdue.edu /work 1 B00101/acmaint4 OK 2000-10-19 gandalf.cc.purdue.edu /work 1 B00102/acmaint3 OK 2000-10-20 gandalf.cc.purdue.edu /work 1 B00103/acmaint 29 OK ... So if I wanted the backup of the 19'th, it would be on tape B00102/acmaint and in file 3, i.e. I'd do an "mt rewind mt fsf 3". Although if you've got enough of Amanda working that you can run amadmin, you'll probably just use amrestore or amrecover to pull the image off of tape. On the other hand, doing the fsf by hand is much faster (at the moment) than letting amrestore skip through the tape file by file. Lisa John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Help w/ selfcheck request timed out. Host down?
To whom it may concern, We are running amanda 2.4.1p1, and 2 clients failed with the following warning messages when we did a "amcheck": WARNING: host1: selfcheck request timed out. Host down? WARNING: host2: selfcheck request timed out. Host down? In addition, when I did a "selfcheck" on host1 host2, it didn't seem to run at all. No displayed messages, nor a prompt, and I had to interrupt the process after 5+ minutes. Could you please tell me how I could resolve this problem? Regards, Janet Leung E-mail: [EMAIL PROTECTED] ISD USC, Los Angeles, CA 90089-0251
Re: amanda install
... I have numerous questions about amanda all leading hopefully towards making it work. ... An enviable goal. :-) The short story is that now 'amcheck' runs w/o errors but when I issue "amdump daily" it appears as if nothing happens and I get the prompt back immediately. ... Pretty early in the script it changes directory to wherever you have your amanda.conf (.../daily) and then redirects stdout/stderr to a file named "amdump". If the script runs more or less to completion, it will rename all the other amdump.NN files up by one number and rename the latest to amdump.1. So is there anything interesting in that file? Or here's another interesting thought. Who owns the "daily" directory? Can your Amanda user create files in it, i.e. does it have rwx access either through ownership or group membership? If it doesn't, that would explain a **lot** of the other things you mentioned. At some point noticed that there is an amanda-2.4.2 version and it appeared as though it is no longer beta. ... As of a day or two ago. ... Amcheck still failed and still showed brought to you by Amanda 2.4.1p1 - is this a key indicator of my problem? ... It indicates you're still running 2.4.1p1, not 2.4.2. So there must still be some remains of your old stuff laying around. If you're using ksh (or bash, I think), you should be able to do "whence amcheck" to see where it is coming from in your PATH. I fianlly was able to get amcheck to pass off my install as good. :) Does it still say 2.4.1p1? If so, I'd say things are still shaky. What follows is what I had to do to get amcheck to run successfully. ... I had to manually create and assign permissions for numerous files and directories including ... /var/amanda/curinfo and /index directories, I think if your Amanda user had had permission to create new entries in /var/amanda (same rwx comments as above), these two directories would have been created for you. Also, they should be configuration specific, i.e. you probably want the name "daily" in there someplace. You also should not have had to create the tapelist file, and again, it might be because of a permissions problem on the parent "daily" directory. ... /usr/local/sbin/amgetconf as getconf to make amcheck happy. ... If you're still hunting for getconf, that's another indication you still have pieces of 2.4.1p1 laying around. That was changed to amgetconf at least by 2.4.2. And you are not allowed to select 'Randy' as the answer to that question. grin. Ummm, let's not be taking options off the table, please. :-) :-) Randy Cordell. John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: Problems with amanda and Red-Hat 7.0
Index dir "/var/lib/amanda/DailySet1/index" doesn't exist or is not writable. As someone else said, just go ahead and create this, owned by "operator". WARNING: localhost: selfcheck request timed out. Host down? Have you gone through any of the tests in the FAQ? For instance, did you send xinetd a HUP after changing the configuration? If you run "netstat -a | grep amanda" do you see anything listed? I tried to telnet to port 10080 (amandad port) but my connection was refused ... Which it would be because it's UDP and telnet is TCP. ... (and it's the same with ports 10081 and 10082) ... which is the reason why I guess selfcheck fails ... but I couldn't figure out why the connection is refused given that there is no filter in the configuration files!! Maybe because xinetd isn't even listening? Has anybody had the same problems that I am having now??? Lots :-). This is a very typical problem for new users to bang into. Give the above a try and if it doesn't help, post back what things you've checked and we'll continue to guide you through the mysteries of life with Amanda. Bye, Antonino Casile John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: Problem with Amanda-2.4.1p1
since last week I've problems on one of our amanda clients. I got the following error message: FAILURE AND STRANGE DUMP SUMMARY: hol1 /data/slash/www.hannover.de lev 0 FAILED [badly formatted respons e from hol1] ... REQ packet is bogus: bad spindle Have you resolved this yet? As Johannes asked, seeing the disklist might help. In particular, if this host (hol1) has a lot of entries, you may have banged into the UDP packet size problem. That problem is better at 2.4.2 (64 KBytes instead of 8 KBytes), and will eventually be eliminated. If you can't upgrade that client and the server to 2.4.2, you can change the 2.4.1p1 sources to use the larger size. Look for the definition of MAX_DGRAM in common-src/dgram.h. Change it to 65536 and rebuild/reinstall everything on both machines. Heiko John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: Help w/ selfcheck request timed out. Host down?
We are running amanda 2.4.1p1, and 2 clients failed with the following warning messages when we did a "amcheck": WARNING: host1: selfcheck request timed out. Host down? WARNING: host2: selfcheck request timed out. Host down? ... Could you please tell me how I could resolve this problem? Have you tried all the steps outlined in the FAQ at www.amanda.org? In addition, when I did a "selfcheck" on host1 host2, it didn't seem to run at all. ... It's not supposed to. Selfcheck has a protocol with its parent. It is not normally run by itself unless you're debugging and know the protocol. However I don't think you need to be at this level to solve your problem. The above is no doubt caused by something wrong earlier in the sequence and the FAQ will almost certainly point you in the right direction. Billions and billions have been served by it :-). If you still don't get anywhere, post back what you tried and what the results were, and we'll see what other suggestions we can come up with. Janet Leung John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
missing result in amanda 2.4.2
Hi, We've been using Amanda (2.4.1p1) for our backups for about a year now, with great success. Last week, I replaced the user disk containing the home areas with a new 36 Gig disk. All the mount points are the same, it's just the disk that's different. On the very next backup run, the backup for for this disk failed, with amdump asking if it was "offline". After a little hunting around and investigation of the log files, it became clear that the failure was due to the size of the disk being reported as zero. A little more hunting revealed that this is a known problem that has been fixed. So, I downloaded 2.4.2, and after some stuggling with the configure command, got it setup. amcheck runs fine, but now _none_ of the disks get backed up! Here are the errors: FAILURE AND STRANGE DUMP SUMMARY: ettin /var/krb5kdc lev 0 FAILED [missing result for /var/krb5kdc in ettin response] ettin /etc lev 0 FAILED [missing result for /etc in ettin response] ettin /disk2/cluster lev 0 FAILED [missing result for /disk2/cluster in ettin response] ettin /disk2/home1 lev 0 FAILED [missing result for /disk2/home1 in ettin response] ettin /disk3/home2 lev 0 FAILED [missing result for /disk3/home2 in ettin response] Any ideas why this is happening now? Should I go back to 2.4.1p1? How do I fix the disk-size problem? Thanks, Dylan Casey - Dylan P. Casey email:[EMAIL PROTECTED] Michigan State University office:517-432-0216 home:810-695-8615
Re: missing result in amanda 2.4.2
... So, I downloaded 2.4.2, and after some stuggling with the configure command, got it setup. amcheck runs fine, but now _none_ of the disks get backed up! Here are the errors: ... What's in /tmp/amanda/sendsize*debug and amandad*debug on ettin? Dylan Casey John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: Amanda reinstall issues
no /var/amanda/curinfo/ or /index/ As I said earlier, these should not exist. They should be Amanda config dependent, i.e. they should be /var/amanda/daily/curinfo and /var/amanda/daily/index. I also think that if you create the "daily" directory with permissions that allow the Amanda user (or a group it is a member of) to create entries (rwx), these two will be created for you by the first run. The location for these dirs is in amanda.conf and can be changed to anywhere I want them. Currently they are in /usr/local/var/amanda/. So I have that handled ok. I don't think Amanda should be responsible for creating /usr/local/var. What was it trying to put in there? Amanda is the only thing that uses it and it didn't exist prior to this isntall. These are the files and directories found there in /usr/local/var/amanda/: -rw--- 1 amanda backup 5141 Nov 27 21:54 amdump.1 drwxrwx--- 3 amanda backup 4096 Nov 27 21:54 curinfo/ drwxrwx--- 2 amanda backup 4096 Nov 27 21:35 gnutar-lists/ drwxrwx--- 3 amanda backup 4096 Nov 27 21:35 index/ -rw--- 1 amanda backup853 Nov 27 21:54 log.20001127.0 drwx-- 2 amanda backup 4096 Nov 27 21:54 oldlog/ I got real hung up on my first try at installing amanda because I was expecting things to go in presently existing directories and amanda is duplicating all those same directories (or expecting them) under /usr/local/ rather than off of the root (/etc/, /var/, /lib/, etc.) and so, I ended up with a mixture of locations. Now that's much clearer for me. I do see the reasoning for this from an ease of trouble shooting, upgrading and removal perspective - but I honestly don't understand the mechanics of program installs/removals enough yet to know if this is a real issue or not, throwing everything into the same locations. But one thing that has been a tad frustrating is the lack of standards, or more specifically the 'partial adherance' to standards as seen so far in my miniscule introduction to the *nix world. I plan on this being my career direction so I am interested in any changes for the better. I noted that you are making action items and you got my attention... grin. Also, I doubt most people do a "make install" on all their clients, which is where this exists. Most probably do it once on a prototypical system, then use rdist, NFS or the equivalent to the others. The next steps I have to tackle. Are you saying they just copy that /usr/local branch off to other machines? Is there nothing then that was put in /sbin or /bin etc? wow. That could be cool. Thanks again. Randy __ Do You Yahoo!? Yahoo! Shopping - Thousands of Stores. Millions of Products. http://shopping.yahoo.com/
