Error messages for prepare to restore, prepare to discover, and the bmrprep command with reference to secure communication in BMR
This section provides information that helps you with troubleshooting the errors that you may encounter while you perform prepare to restore (PTR) or prepare to discover (PTD) operations and while you use the bmrprep command.
Table: Error messages with respect to secure communication in BMR
Error message | Description |
|---|---|
Add an appropriate host entry or host mapping for <Name of the host> and retry the operation. | To restore BMR configurations of NetBackup 8.1.1 and later, a valid host ID to host name mapping for the selected host name must be present. Use the nbhostmgmt command for adding a host entry in the host database or for host ID to host name mappings. For more information about the nbhostmgmt command refer NetBackup Command Reference Guide https://www.veritas.com/support/en_US/article.DOC5332 Scenario 1: The host that you intend to restore may have multiple host names associated with it or it may be referred by short name or FQDN in different contexts. If any of those host names have an entry in the host ID to host name mappings database, you need to add a mapping for it with the host name that you intend to restore using the nbhostmgmt -add command to add a new mapping to an existing host entry. such as short name, FQDN and so on Scenario 2: If none of the host names associated with the host that you intend to restore have entries in the host ID to host name mappings database, you need to add the required host entry in the host database. This may occur in a BMR A.I.R. setup. |
Shared Resource Tree version <Version> is incompatible with client configuration version <Version>. . | To restore BMR configurations of NetBackup 8.0, you must use Shared Resource Tree (SRT) with NetBackup client version of 8.0 installed in the SRT. Shared Resource Tree (SRTs) with NetBackup 8.1.1 or later installed in them are not supported for restoring BMR configurations of NetBackup 8.0. Similarly, to restore BMR configurations of NetBackup 8.1.1 or later, you must use Shared Resource Tree (SRT) with NetBackup client version of 8.1.1 or later installed in the SRT. The usual conditions that the SRT version is greater than or equal to the BMR configuration version apply. |
Reset the host attributes for <Name of the host> and retry the operation. | To restore BMR configurations of NetBackup 8.0 for a host that is known to the master as communicating securely (For Example: NetBackup 8.1 and above hosts), you must reset the host for a successful communication. For more information about resetting host attributes, refer NetBackup Security and Encryption Guide |
Reset host attributes for all hosts with the mapping name <Mapping Name> and retry the operation. | A host name may be associated with multiple host IDs. For example: In a clustered environment. Some or all of those hosts may be known to the master as communicating securely (For Example: NetBackup 8.1 and above hosts). For restoring BMR configurations of NetBackup 8.0 or earlier for such hosts, you must reset all of those hosts for successful communication. For more information about resetting host attributes, refer NetBackup Security and Encryption Guide |
Configuration version of the specified host is 8.1, which is not supported by BMR. | Restoring BMR configurations of NetBackup 8.1 version is not supported. |
Set the 'autoreissue' parameter for one of the host IDs of <Name of the host> and retry the operation. | A host name may be associated with multiple host IDs. For example: In a clustered environment. In such scenarios, you must set the parameter for only one of the host IDs which you intend to restore. For more information about the host mapping, refer to the nbhostmgmt command in the NetBackup Command Reference Guide https://www.veritas.com/support/en_US/article.DOC5332 For more information about the autoreissue parameter, refer NetBackup Security and Encryption Guide. |
Authorization failed. A web login is required. Run the <Command Name> command to log in. | For a successful execution of bmrprep command, a web login is required. Perform a web login using the bpnbat command before you execute bmrprep command For more information about the bpnbat command, refer to the bpnbat command in the NetBackup Command Reference Guide |
BMR client <Name of the client> is ready to be restored. This operation is valid for a limited period of time. The default is 48 hours. Boot the client to proceed. | To restore BMR configurations of NetBackup 8.1.1 and later, you are provided with a limited period of time. The default is 48 hours. You can edit or update the default validity of 48 hours to the desired value using For more information about the autoreissue validity configuration setting, refer to the NetBackup Security and Encryption Guide. https://www.veritas.com/support/en_US/article.DOC5332 Note: This is not a requirement to restore BMR configurations of NetBackup 8.0. |
BMR client <Name of the client> is ready to be discovered. This operation is valid for a limited period of time. The default is 48 hours. Boot the client to proceed. | To discover BMR configurations of NetBackup 8.1.1 and later, you are provided with a limited period of time. The default is 48 hours. You can edit or update the default validity of 48 hours to the desired value using For more information about the autoreissue validity configuration setting, refer to the NetBackup Security and Encryption Guide. https://www.veritas.com/support/en_US/article.DOC5332 Note: This is not a requirement to restore BMR configurations of NetBackup 8.0 and earlier versions. |
The specified IP address <IP address> is not associated with the host name <Name of the host>. Specify an appropriate IP address for successful Prepare To Discover operation. | If the IP address that you have specified during Prepare to Discover (PTD) operation for a particular BMR client is not associated with that client, the PTD operation fails. You must ensure that you have entered the appropriate IP address. |
The Prepare To Discover operation is not successful, because the specified IP address cannot be resolved. | If the IP address that you have specified during Prepare to Discover (PTD) operation cannot be resolved, the PTD operation fails. You must ensure that you have entered the appropriate IP address. |