|
|
Line 1: |
Line 1: |
| == What kind of trouble? ==
| | #REDIRECT [[:Category:Troubleshooting]] |
| | |
| [[amcheck issues]] | |
| | |
| [[amdump issues]]
| |
| | |
| [[amandad issues]]
| |
| | |
| [[amfetchdump issues]]
| |
| | |
| [[amlabel issues]]
| |
| | |
| [[amrecover issues]]
| |
| | |
| [[amrestore issues]]
| |
| | |
| [[amverify issues]]
| |
| | |
| [[Recovering amanda configuration]]
| |
| | |
| [[NFS issues]]
| |
| | |
| === 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:
| |
| | |
| | |
| | |
| 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.
| |
| | |
| === Reality Check Your Tape Drive ===
| |
| | |
| You can use a low level command to check the status of your tape drive, substituting the device name of your drive:
| |
| | |
| '''On FreeBSD:'''
| |
|
| |
| mt -f /dev/rsa0 status
| |