No index records for host-disk

From wiki.zmanda.com
Revision as of 16:28, 25 December 2005 by Paddy (talk | contribs)
Jump to navigation Jump to search
Causes
  • The most common cause of this problem is not having enabled index generation in amanda.conf. The `index yes' 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.

  • Another possibility is that amrecover is not selecting the configuration name that contains the backups for the selected disk. You may specify a configuration name with the `-c' switch, when you invoke `amrecover'.
  • Amrecover is contacting the wrong 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.

See more amrecover issues

Retrieved from ‘http://wiki.zmanda.com/index.php?title=No_index_records_for_host-disk&oldid=2169’