No way would I call this a bug. Because of the business AMANDA is in, answering multiple concurrent requests could be dangerous. There's no reason that your backup software shouldn't know every machine by one, and only one name, no matter how many names your users know it by. There are places in IT to obscure what's going on, this ain't one of them.
If you're worried about your indexes being broken when you move a disk, how often do you really move a disk? Compare that to how often you restore, or better, how often you test your restores. You might be chasing a ghost, Scooby. It might make sense to also be prepared to do non-index recoveries. (Be prepared, test both monthly!) If you really want to do this, run multiple amdumps per day, and alter the disklist in between. Make sure one is done before the next starts. IIRC, The timeout is because inetd doesn't start a second amandad for the second connection request. So it simply goes unanswered. This might be a good thing to put some code into: On amandad startup, if it detects another amandad running, it returns some sort of "HOST BUSY" message. Probably easier to do in 2.5 with the NOP feature. > -----Original Message----- > From: Toralf [mailto:toralf@;kscanners.com] > Sent: Thursday, October 17, 2002 1:40 PM > To: Anthony Valentine > Cc: Amanda Mailing List > Subject: Re: Host name aliases in disklist > > > > On Thu, 2002-10-17 at 03:03, Toralf Lund wrote: > > > > Hi, > > > > your assumption about the hostnames is correct. > > > > > > > > What you are doing is one of the big NO!NO!'s of amanda. > > > Just like I suspected ;-/ > > > > > > > > > > Never list a single host in multiple concurent amanda runs, or, > > > > in your case, with different names in a single amanda > > configuration. > > > > amandad can only handle one request at the same time. > > > Yes, I knew that. Which is why amdump/planner should do a host > > lookup and > > > base it's decision on IP addresses. > > > > > > > > Only solution is to use only one hostname per physical host in > > disklist. > > > I'd say the failure to handle aliases is a *BUG*! > > > > I don't think he is saying that it's the aliases that are a problem, > > but > > rather having the same host in the disklist twice as two separate > > aliases. > The problem seems to be that Amanda doesn't understand the concept of > aliases, i.e. that different hostnames may refer to the same physicl > host. > > > > > So, if that is true, you could have an entry for either > amanda-server > > or > > fileserv, but not both only because they are the SAME host. > > > > Amanda can only handle one connection at a time, which would explain > > why > > amanda-server will time-out while fileserv is backed up > fine, and then > > vise versa. > It's still a bit surprising to me that I get a timeout.�I would > normally expect a "host busy" message. > > > > > > > > > > No other way out there. > > > Again, this is really a shame. It causes extra work & a > whole lot of > > mess > > > in the indexes etc. if you move disks around a bit. > > > > > > - Toralf > > -- > > UNIX was not designed to stop you from doing stupid things, > > because that would also stop you from doing clever things. > > >
