Veritas NetBackup™ Bare Metal Restore™ Administrator's Guide

The best methodology for debugging this error message involves the following steps:

1. Perform a Prepare-to-restore operation from the NetBackup Administration Console or from the command line. If an error is encountered, then one of the below listed causes is at fault. Use normal NetBackup catalog query information to verify that a backup image is available using the correct policy type. Also, verify that the System State/ Shadow Copy Components were backed up properly. Also verify that the Bare Metal Restore software directory on the client was also backed up. If the Prepare To Restore operation is successful, the backup image information is valid. This in turn points to a problem in the BMR restore environment on the client or a network setting on the master server. Items that need to be verified as good in the restore configuration:

   • Check the 'Network Interfaces' section and ensure that the MAC address is correct and is the one being used during the restore. Verify that a network cable is attached to correct port on both the client NIC and the switch.

   • Check the "Hosts" section and verify that valid entries (host name and ip-address) exist for the NetBackup master server and media server, as required.

   • Look in the bmrrst log on the master server to see the progress of the restore. To determine the root cause on the restoring client:

2. Cancel and exit from the restore wizard. This should place you in the main menu.
3. Move the mouse to a location in the upper left-hand corner of the main screen, near the gear shaped icon. When the mouse pointer changes from an arrow to a hand, right-click the mouse. This opens a command-line window.
4. Change directory to X:\BMR\NBU\bin.
5. Execute the command,

   bpclimagelist -client $CLNT_NAME -T echo %ERRORLEVEL%

   The 'echo' command displays the return code of the command. The bpclimagelist command will fail to gather catalog backup image information for the following reasons:

   • Could not contact the master server (rc=25). This happens if the client has connected on the wrong interface port or has an invalid or incomplete host name and ip-address information for the master server. The fact that the client could initially access the client configuration is not relevant. At the time of the failure, the client network interfaces were modified to match what was in the restore configuration specified for the restore. The values entered on the first input page have been modified to match the configuration values.

   • The master server could not respond back to the client port (rc=23). Possible causes are missing client reverse lookup information, either in the Server's DNS entries or hosts file or invalid routing back to the client

   • The master server does not see the restoring client as a valid client (rc=131, 133, 135). The ip-address used by the client resolved to a different name than in the configuration, or the client does not have permission to perform list/restore requests. One way to resolve this is to place a temporary entry in the 'hosts' file of the master server and media server. This entry must match the data information found'Network Interfaces' section of the restore configuration used for the restore. Also check the Host Properties > Master Server > Client Attributes of the NetBackup Administration Console to ensure that the client has permissions to perform list and restore operations

   • The NetBackup master server does not have a valid backup image (rc=227).