Troubleshooting: Difference between revisions
Jump to navigation
Jump to search
Paul.bijnens (talk | contribs) |
Paul.bijnens (talk | contribs) m (Renamed titles - avoid linking throug redirect) |
||
| Line 1: | Line 1: | ||
== What kind of trouble? == | == What kind of trouble? == | ||
[[amcheck | [[amcheck issues]] | ||
[[amdump | [[amdump issues]] | ||
[[amandad | [[amandad issues]] | ||
[[amfetchdump | [[amfetchdump issues]] | ||
[[amlabel | [[amlabel issues]] | ||
[[amrecover | [[amrecover issues]] | ||
[[amrestore | [[amrestore issues]] | ||
[[amverify | [[amverify issues]] | ||
[[Recovering amanda configuration]] | [[Recovering amanda configuration]] | ||
Revision as of 19:38, 9 December 2005
What kind of trouble?
Recovering amanda configuration
General networking
- Issue
- Amanda server and backup client are connected to the Internet via ADSL. It seems that when Amanda on the backup client does a DNS lookup for my Amanda server, it sees something like:
[email protected]
which is generated by the ISP. Since the machine has a static IP address, the really-long-and-annoying-hostname shouldn't change. How to use backup server's hostname actual hostname (amanda.mydomain.com) instead of the long ISP name?
- Solution
- Define the IP address in the hosts file (/etc/hosts) on the backup client
XXX.XXX.XXX.XXX amanda.mydomain.com
- Change the name lookup order in /etc/nsswitch.conf file to
hosts: files dns
The lookup order, eg. files dns (and/or ldap, nis, ...) so that hosts file is searched before name servers.