|
|
| Line 1: |
Line 1: |
| {{Troubleshooting Header}}
| | #redirect [[No index records for host-disk]] |
| =Problem=
| |
| | |
| [[amrecover]] gives | |
| No index records for host: ''hostname''. Have you enabled indexing?
| |
| or
| |
| No index records for disk: ''disk''. Invalid?
| |
| | |
| =Explanation=
| |
| * The most common cause of this problem is not having enabled index generation in [[amanda.conf]]. The <tt>index yes</tt> option must be present in every dumptype for whose disks indexes should be generated. Indexes are currently generated at backup-time only, so, if a backup was performed without creating an index, you won't be able to use [[amrecover]] to restore it; you'll have to use [[amrestore]].
| |
| | |
| * Amrecover is not selecting the configuration name that contains the backups for the selected disk. User can specify a configuration name with the `-c' switch to [[amrecover]].
| |
| | |
| * Amrecover is contacting the wrong index server. Note that some packaged distributions have "localhost" as compiled in default index server. Specify the index server and tape server explicitly with:
| |
| # amrecover Config -s amandaserver.example.com -t amandaserver.example.com
| |
| | |
| To find the builtin default values for the above do:
| |
| | |
| $ amadmin x version | grep DEFAULT_CONFIG
| |
| $ amadmin x version | grep DEFAULT_SERVER
| |
| $ amadmin x version | grep DEFAULT_TAPE_SERVER
| |
| | |
| The first command shows the default configuration, the second command shows the default index server, and the last command shows the default tape server.
| |
| | |
| * If there are defunct processes running on the Amanda client after amrecover command failure, the directory where data is being restored to is not writable. Check the directory/file permissions. During the backup operation, the client uses the <tt>/tmp/amanda</tt> directory, and it must be writable by the Amanda user to create indexes. If [[amrecover]] is restoring files to <tt>/tmp</tt>, then it must be writable.
| |