Status 1: Bare Metal Restore configuration capture fails causing backup job to complete with Status 1

Article:TECH135304

|

Created: 2010-01-08

|

Updated: 2012-03-09

|

Article URL http://www.symantec.com/docs/TECH135304

 

>>"The kernel version of the SRT,'Generic_141444-09' is not same as the kernel version of the client 'Generic_142909-17'"

Generic_141444-09 indicates SRT is of Solaris10Update8 and Generic_142909-17 means your client is of Solaris10Update9.

It means you are using lower version SRT to recover client of higher kernel version, this may result in failures. Please try restore using SRT of Solaris10Update9.

If you still see below error messages during restore, check whether your client in restore environment is able to ping master server or not. And provide the BMR restore(bmrrst)  logs present on Masterserver under logs folder.

>> V-128-749 Operation failed due to network problem.
>> [Error] V-122-3 Operation failed.
>> ERROR: Failed to retrieve "/tmp/0A0A38EC.restore".
>> V-128-749 Operation failed due to network problem.
>> [Error] V-122-3 Operation failed.

 

Hello all,

Thanks for your response.

I have tried "Prepare to Restore" using command line also but its getting failed with the same error.

And The ping response from client to master server is getting fine.

The bmrrst logs giving error as "Checking_VxSS_Credentials".

While creating bootable image from boot server,its asking one question as 'would you like to configure 'bmr1' as your netbackup client?'.Here 'bmr1' is my boot server host name.

Is it required to give the client host name here.('bmr2' is my solaris client hostname')

Also Once the shared resource tree creation completed using ./bmrsrtadm, I have selected 2nd option as "Create a new CD image based Shared resource tree",then burn the iso image into CD and boot the client using the same.

Please find the attached screen shots for boot image creation and kindly suggest me is it proper way or not.

Meanwhile I will try to create the SRT of Solaris10Update9.but that is giving just as a warning only,then it is prompting for 'ready to start restoration of the client'.

Any way will try out.

 

Thanks and Regards,

Vishnavi

 

Hello,

 

Can you just tell me the procedures for network boot.

As per document ,start the network boot by entering the following command (network_device

is the device that points to the BMR boot server):

boot network_device.

But what should we requires to enter in place of network_device?Is it Ip/hostname of boot server?

 

Thanks and Regards,

Vishnavi

If you are using "bmrprep" command line, please make sure that you give "-logging" switch. Otherwise, logging will not be enabled.

 

>>While creating bootable image from boot server,its asking one question as 'would you like to configure 'bmr1' as your netbackup client?'.Here 'bmr1' is my boot server host name. Is it required to give the client host name here.('bmr2' is my solaris client hostname')

Its okay, you can give any name as netbackup client name while creating SRT. This SRT can be used to restore other clients of Compatible OS level.

 

The way you have created Media Based SRT looks fine. One thing I observed is, during SRT creation while providing servername , you gave just hostname(didn't mention fully qualified domain hostname(FQDN)). I hope  that is your your masterserver complete name (hostname that was given while installing Masterserver).  Please makesure you give same name.

Rest all process of creating Mediabased SRT looks fine.

 

>> But what should we requires to enter in place of network_device?Is it Ip/hostname of boot server?

The ethernet device of client on whic you want to do networkboot. For example, if you have 4 NICs in you client and you want to boot on 2nd NIC through which you can connect to Bootserver, give below command on OK prompt.

{0} ok. boot net2

 

By default "boot net" boots to first nic of your client.

 

Thanks..

 

Whether we have to follow any settings/procedures before doing network boot.

 

To clarify on above post, when Katlamudi mentioned one Bootserver to be active, I believe he meant to make sure that the DHCP server of only the required boot server is enabled. In case you have any other boot server in your subnet running DHCP and if your network boot request is going to that other boot server then you need to disable the DHCP on the other boot server.

Also typically the (Failed to retrieve "/tmp/0A0A38EC.restore") type of errors come in case you have two subnet configurations on your client, where the backup happened through one of the NIC and the recovery is happening via other subnet.

For this you will have to make sure that the client machine boots over the primary NIC (that was considered primary during PTR operation and created the corresponding "NIC_HEX_ADDRESS.*" file accordingly.).

In case you have multiple NICs, make sure that you are configuring the client IP details in restore environment for the correct NIC whose hex address will be  0A0A38EC in your case.

Also when BMR restore fails at the command prompt, you can check /etc/hosts file to confirm that correct host-ip details are set.

Regards,

Rishi Raj

 

 

Thanks for update...

Please claify me,Is it required to create the file "/tmp/0A0A38EC.restore" before starting restoration Or else is it creating automatically.

And also in my client end only one NIC card is configured.

 

Thanks and Regards,

Vishnavi