No index records for host-disk: Difference between revisions
Jump to navigation
Jump to search
Paul.bijnens (talk | contribs) m (Why does `amrecover' report `no index records' or `disk not found'? moved to Amrecover: No index records for host/disk) |
No edit summary |
||
| Line 1: | Line 1: | ||
; 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]]. | 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'. | * 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: | |||
Specify the index server and tape server explicitly with: | |||
# amrecover Config -s amandaserver.example.com -t amandaserver.example.com | # amrecover Config -s amandaserver.example.com -t amandaserver.example.com | ||
Revision as of 16:28, 25 December 2005
- 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