No index records for host-disk: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
; Causes : | ; Causes & Solutions : | ||
* 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. | * 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]]. | |||
* | * 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, when `amrecover' command is invoked. | ||
* Amrecover is contacting the wrong index server. Specify the index server and tape server explicitly with: | * Amrecover is contacting the wrong index server. Specify the index server and tape server explicitly with: | ||
| Line 17: | Line 16: | ||
The first command shows the default configuration, the second command shows the default index server, and the last command shows the 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. Amanda client during backup operation uses /tmp directory and must be writable by the Amanda user to create indexes. If the amrecover is restoring files to /tmp directory, it must be writable. | |||
---- | ---- | ||
See more [[amrecover issues]] | See more [[amrecover issues]] | ||
Revision as of 16:36, 25 December 2005
- Causes & Solutions
- 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.
- 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, when `amrecover' command is invoked.
- 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.
- 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. Amanda client during backup operation uses /tmp directory and must be writable by the Amanda user to create indexes. If the amrecover is restoring files to /tmp directory, it must be writable.
See more amrecover issues