No index records for host-disk: Difference between revisions

From wiki.zmanda.com
Jump to navigation Jump to search
No edit summary
 
(reworked)
Line 3: Line 3:
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.  


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'. The default configuration name can only be specified at Amanda configure time (--with-config=NAME).  
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'.
 
Yet another possibility is that you are 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.


----
----


Sometimes it is also useful to specify the index-host and the tapehost by using the switches -s and -t.
See more [[amrecover issues]]

Revision as of 22:53, 12 December 2005

--- This text was originally contributed to the AMANDA-FAQ-O-Matic by [email protected]. ---

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'.

Yet another possibility is that you are 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