Requirements and considerations for BMR

[DPO]

RHEL Linux master server with NetBackup version 7.5.0.5. Configured BMR master server (on the master server) and boot server (on the client) and took backup on to media server deduplication pool (puredisk). Initially I received the below error and after somtime backup completed successfully.

5/16/2013 15:44:46 - Error bpbrm (pid=20713) [ERROR][proxy_open_server_v7]CORBA::SystemException is caught in proxy_open_server_v7, minor = 1330446338, status = 1, info = system exception, ID 'IDL:omg.org/CORBA/TRANSIENT:1.0'.OMG minor code (2), described as '*unknown description*', completed = NO
05/16/2013 15:44:46 - Error bpbrm (pid=20713) libsts opensvh() 13/05/16 06:14:46: v11_open_server failed in plugin /usr/openv/lib/libstspinbostpxy.so err 2060057
05/16/2013 15:45:46 - Error bpbrm (pid=20713) [ERROR][proxy_get_server_prop_byname_v8]CORBA::SystemException is caught in proxy_get_server_prop_byname_v8, minor = 1330446338, status = 1, info = system exception, ID 'IDL:omg.org/CORBA/TRANSIENT:1.0'.OMG minor code (2), described as '*unknown description*', completed = NO
05/16/2013 15:45:46 - Error bpbrm (pid=20713) sts_get_server_prop_byname failed: error 2060057 - retrying
05/16/2013 15:46:47 - Error bpbrm (pid=20713) [ERROR][proxy_get_server_prop_byname_v8]CORBA::SystemException is caught in proxy_get_server_prop_byname_v8, minor = 1330446338, status = 1, info = system exception, ID 'IDL:omg.org/CORBA/TRANSIENT:1.0'.OMG minor code (2), described as '*unknown description*', completed = NO
05/16/2013 15:46:47 - Error bpbrm (pid=20713) sts_get_server_prop_byname failed: error 2060057 - retrying
05/16/2013 15:47:48 - Error bpbrm (pid=20713) [ERROR][proxy_get_server_prop_byname_v8]CORBA::SystemException is caught in proxy_get_server_prop_byname_v8, minor = 1330446338, status = 1, info = system exception, ID 'IDL:omg.org/CORBA/TRANSIENT:1.0'.OMG minor code (2), described as '*unknown description*', completed = NO
05/16/2013 15:47:48 - Error bpbrm (pid=20713) sts_get_server_prop_byname failed: error 2060057 - retrying
05/16/2013 15:48:50 - Error bpbrm (pid=20713) [ERROR][proxy_get_server_prop_byname_v8]CORBA::SystemException is caught in proxy_get_server_prop_byname_v8, minor = 1330446338, status = 1, info = system exception, ID 'IDL:omg.org/CORBA/TRANSIENT:1.0'.OMG minor code (2), described as '*unknown description*', completed = NO
05/16/2013 15:48:50 - Error bpbrm (pid=20713) sts_get_server_prop_byname failed: error 2060057 - retrying
05/16/2013 15:49:51 - Error bpbrm (pid=20713) [ERROR][proxy_get_server_prop_byname_v8]CORBA::SystemException is caught in proxy_get_server_prop_byname_v8, minor = 1330446338, status = 1, info = system exception, ID 'IDL:omg.org/CORBA/TRANSIENT:1.0'.OMG minor code (2), described as '*unknown description*', completed = NO
05/16/2013 15:49:51 - Error bpbrm (pid=20713) sts_get_server_prop_byname failed: error 2060057

1) I do not have DHCP in our environment. Is it necessary to have DHCP for BMR ?

2) What are the important considerations for BMR.

3) Any idea why I received the above error  in the Detailed status of job.(But backup completed successfully).

[Mark_Solutions]

Those errors look more like a client doing client side de-dupe and not being able to resolve or connect to the puredisk server.

For BMR you need a boot server for each operating system that you want to protect

Lots of requirements for Unix systems - all covered from P19 onwards of the BMR Admin Guide

Redhat does require compat-libstdc+, tftp-server and dhcp

Most other operating systems also require the dhcp component installing

Your error log looks like the client trying to do client side de-dupe - looks like it failed to connect to your puredisk and so if it completed successfully i assume it then did the backup using media server de-dupe - this should have been listed within the job details somewhere

Hope this helps

Latest BMR Admin Guide here: http://www.symantec.com/docs/DOC5163

[mandar_khanolka]

This above error is not definitely because BMR problem. Looks like some problem happened while allocating storage on media server (not quite sure though)

1) I do not have DHCP in our environment. Is it necessary to have DHCP for BMR ?

Not compulsory. You can also recover your client using media based boot recovery method. DHCP server is required to be setup only in case of NW based BMR recovery. Also BMR boot server internally handles dhcpd.conf entries automatically for client being recovered. Only a basic block needs to be added to dhcpd.conf and start the service. Refer bmr admin guide for more details. In case of media no NW services are required to be setup. and even used during recovery.

thanks.

mandar

[DPO]

Thanks for the prompt response. So I need not install dhcp on my boot server right and need not configure

/etc/dhcpd.conf ?

I installed only tftp-server , compat-libstdc++ and xinetd only linux boot server.

[Mark_Solutions]

You do need it but just the very basics so that it runs for its own internal processing - so a very minimual dhcp.conf

[mandar_khanolka]

•  
• E.g. /etc/dhcpd.conf   

log-facility local7;

ddns-update-style none;

ignore unknown-clients;

subnet 192.168.6.0 netmask 255.255.255.0 {

default-lease-time            600;

max-lease-time             7200;

option domain-name         "punbmr.com";

option broadcast-address   192.168.6.255;

option domain-name-servers 192.168.0.3,10.217.160.131;

option routers             192.168.6.1;

}

[DPO]

I have setup BMR as stated above and took the backup. Backup completed successfully. But the recovery is failing with the error as attached.

Note -- We don't have DNS in our network.

[mandar_khanolka · Accepted solution]

Looking at the error, the failure cause is related to the NW service configuration on the boot server.

Please confirm if you see below daemons running:

1. nfsd

2. tftpd

3. dhcpd

You can turn on debug log with level 6 on the boot server and repeat PTR operation to get more details on the failure.

To turn on debug level 6, on boot server, open nblog.conf file and set debugloglevel=6

Restart NB services on boot server. Do PTR. Check bmrd.log file on the boot server for error details.

Thanks.

Mandar

[DPO]

Mandar,

Installed below packages on my master server. I'm not able to start dhcpd service. Also note that my linux client is not accessible now. Its status is Unknow in Vcenter console.

I could not figure out what I'm missing.

[root@masterserver ~]# yum search dhcp
Loaded plugins: product-id, security, subscription-manager
Updating certificate-based repositories.
Unable to read consumer identity
========================================================================================= N/S Matched: dhcp =========================================================================================
dhcp-common.x86_64 : Common files used by ISC dhcp client and server
dhcp.x86_64 : Dynamic host configuration protocol software

  Name and summary matches only, use "search all" for everything.
[root@masterserver ~]#
[root@masterserver ~]# yum search tftp
Loaded plugins: product-id, security, subscription-manager
Updating certificate-based repositories.
Unable to read consumer identity
========================================================================================= N/S Matched: tftp =========================================================================================
tftp-server.x86_64 : The server for the Trivial File Transfer Protocol (TFTP)

  Name and summary matches only, use "search all" for everything.
[root@masterserver ~]#
[root@masterserver ~]# yum search compat-libstdc++
Loaded plugins: product-id, security, subscription-manager
Updating certificate-based repositories.
Unable to read consumer identity
=================================================================================== N/S Matched: compat-libstdc++ ===================================================================================
compat-libstdc++-33.x86_64 : Compatibility standard C++ libraries

  Name and summary matches only, use "search all" for everything.

------------------------------------------------------------------------------------------------------------------------------------------------------------------------

[root@masterserver ~]# ps -ef | grep nfs
root      3270     2  0 07:14 ?        00:00:00 [nfsd4]
root      3271     2  0 07:14 ?        00:00:00 [nfsd4_callbacks]
root      3272     2  0 07:14 ?        00:00:00 [nfsd]
root      3273     2  0 07:14 ?        00:00:00 [nfsd]
root      3274     2  0 07:14 ?        00:00:00 [nfsd]
root      3275     2  0 07:14 ?        00:00:00 [nfsd]
root      3276     2  0 07:14 ?        00:00:00 [nfsd]
root      3277     2  0 07:14 ?        00:00:00 [nfsd]
root      3278     2  0 07:14 ?        00:00:00 [nfsd]
root      3279     2  0 07:14 ?        00:00:00 [nfsd]
root      3281  3091  0 07:14 pts/0    00:00:00 grep nfs

[root@masterserver ~]# /etc/init.d/xinetd status
xinetd (pid  1796) is running...
[root@masterserver ~]#
[root@masterserver ~]# ps -ef | grep tftp
root      3325  3091  0 07:16 pts/0    00:00:00 grep tftp

[root@masterserver ~]# /etc/init.d/dhcpd status
dhcpd is stopped

[mandar_khanolka]

what happens if you run below?

/etc/init.d/dhcpd start

Do you see any dhcp daemon errors?

You can also run ntsysv gui tool to enable tftp, nfs and dhcp services.

Thanks.

Mandar

[huanglao2002]

dhcp server is not the necessary resource for BMR restore.

You can try use cd/dvd boot.

and then try to use network start.

[Jaime_Vazquez]

The error in the backup is not associated with BMR.

The network based services are only required if network boot is the desired method for doing a BMR system recovery.

   1. dhcpd - "service dhcpd status"

   2. nfs - "service nfs status"

   3. tftp - this is a listening service through xinetd.

The Prepare To Restore error shown in the screen shot can occur if:

1. One of the above noted services is not started.

2, The 'dhcpd.conf' file is not not properly set up.

3. The IP address in the restore configuration does not resolve back to the restoring client's host name, as seen on the Boot Server.

If using media (CD/DVD/ISO) as the boot method, none of the above is required.  The media itself becomes the Boot Server.

If all else fails, you can always open a support case with NetBackup support.

[inn_kam]

Requirements for Bare Metal Restore (BMR) Boot Servers

Article:TECH87607

|

Created: 2009-01-19

|

Updated: 2011-12-29

|

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

[Jaime_Vazquez]

The above shown article (TECH87607) covers Boot Server requirements from a higher overall  level.  It does not cover required services.