After a successful verification, ZMC displays the following message:
On Solaris 10 servers (both x86 and sparc architectures), Verify installation will fail due to lack of xinetd support. This failure can be ignored. Error message will appear as shown in the figure below.
Tip:
Success implies that it is technically feasible to backup data on Amanda Server while treating it as an Amanda Client.
Nothing is implied that this is an optimal overall way to organize user's backup needs.
ZMC's checks on a Client Host can give rise to a wide variety of error messages!
The error messages are verbose to help users to determine what caused the error.
Here the Host name specified in the Backup What page (though valid in terms of formatting rules) does not correspond to any entry in the Domain Name Server.
Hence DNS cannot provide any IP address for the next step of checking to begin.
Go back to the Backup What page and correct the entry so that it corresponds to a DNS name.
Come back to this page and verify the Amanda client without having to go through the previous successful checks.
Verification messages may have hyper links (selfcheck request failed in this example).
Clicking on the hyper link will provide additional information about the message from Zmanda Network Knowledgebase or the Amanda wiki.
Windows Client Error Messages
When Users are verifying Zmanda Client for Windows, error messages appropriate to their context will appear.
In the example above, the Zmanda Window Client had not been started on the client.
When the term 'localhost' is used in a DLE instead of fully qualified domain name, and if IPv6 is enabled on Amanda server and Linux kernel does not have IPv6 kernel module loaded, the ZMC server configuration verification will fail with "Address family not supported by protocol" error message.
To fix the problem, change "flags=IPv6" in /etc/xinet.d/amandaserver file to "flags=IPv4". XXX Knowledge Base Article