Video Screencast Help

Setting up a Linux BMR Boot server

Created: 23 Nov 2012 | 15 comments
Sacha Brown's picture

I am attemping to set up a linux client (RedHat) to be specific but I get and error when the following steps are performed.

 

To setup a BMR Boot Server on Linux

1) Navigate to the directory where NBU is installed

/usr/openv/netbackup/bin

2) Run the following command on the boot server host

./bmrsetupboot -register

Please see attached for a screenshot of the exact error that occurred.

I tried this command on a mixture of both virtual and physical linux servers.

One thing to note is that there are 32 bit Linux server and we had no other option but to install NBU 6.5.4 since NBU 7.5 does not support 32 bit Linux servers. The other 64 bit servers we were able to install NBU 7.5 without any issues.

The only issue is getting to register one of these servers as the Linux Boot server.

 

Comments 15 CommentsJump to latest comment

Nagalla's picture

servers is  resolving the IP 127.0.0.1 , which is loopbackup address..

you need to check your hosts file and IP configuration.. and make sure it has a valid IP and then try.. 

Joseph_TKLee's picture

I have configured Solaris BMR boot server easily and successfully.

But I don't configure linux as I don't need it.

When I prepared the BMR things, I added preparation tasks for linux bmr boot server.

Please refer to the pre-tasks below to solve your issue.

**************************************************************************************************

            Red Hat Linux system prerequisites

                        The following system prerequisites apply only to Red Hat Linux systems:

                        ■ Install the following RPM packages (unless already installed):

                                     # rpm -aq | egrep –i ‘compat-libstdc|tftp|dhcp’

                                    - compat-libstdc++

                                    - tftp-server

                                    - dhcp

                        ■ Enable the tftp service as follows:

                                    - Edit the /etc/xinetd.d/tftp file and change disable = yes to disable = no.

                                    - Start the service by running the following command:

                                                /etc/init.d/xinetd restart

                        ■ Create a /etc/dhcpd.conf file and configure it to define the networks it serves.

                            You do not have to define host information; hosts are added and removed as needed by the BMR software. The following is an example configuration:

                                    log-facility local7;

                                    ddns-update-style none;

                                    ignore unknown-clients;

                                    subnet 10.10.5.0 netmask 255.255.255.0 {

                                    default-lease-time 600;

                                    max-lease-time 7200;

                                    option domain-name "example.com";

                                    option broadcast-address 10.10.5.255;

                                    option domain-name-servers 10.10.1.4,10.88.24.5;

                                    option routers 10.10.5.1;

                                    }

                                    To verify the /etc/dhcpd.conf file syntax, restart the daemon and ensure

that it starts successfully by running the following command:

                                    /etc/init.d/dhcpd restart

************************************************************************************

Hope it helps.

Cheers,

Joseph_TKLee's picture

FYI, I love the screenshot attached as it makes me get better-understanding of your problem. :)

Cheers,

From Non-english speaker of South Korea.

Sacha Brown's picture

Hi Guys,

 

I've not been able to try the steps as suggested. Will keep you all posted.

 

Thank You

 

Khamatee Brown

Systems Engineer 2

| MCP | MCTS | MCITP |

Backup Exec STS| Netbackup STS

mandar_khanolkar's picture

There is not "bmrsetupboot -register" in case of 65x nb client. From 7.x onwards bmr boot server needs to be explicitly registered with bmr master using "bmrsetupboot -register" command. The reason is 7.x bmr boot server is integrated with NB client installation.

In case of 65x case, if your nb client is already registered with nb master. And bmr master server is setup, then bmr boot server package installation should register it successfully.

thanks.

mandar

Sacha Brown's picture

Hi Mandar,

 

I am not fully understanding what your are trying to say. Please excuse me. From wha I get is that 6.5 Linux does not support BMR so it cannot be registered as a boot server.

 

From 7.x onwards bmr boot server needs to be explicitly registered with bmr master using "bmrsetupboot -register" command.

I did attempt to register with BMR Master Server using the command but got the issue as seen attached.

 

In case of 65x case, if your nb client is already registered with nb master. And bmr master server is setup, then bmr boot server package installation should register it successfully.

Can you please explain above?

From my understanding to restore windows server a windows boot server is resquired. Since the master server is Windows it is designated as the windows boot server. We have Linux servers so i would like to designate a Linux client as a Linux boot server. You are saying that 6.5 cannot be used as a boot server or is it that it doesn't have the BMR feature.

 

Thank You

 

Khamatee Brown

Systems Engineer 2

| MCP | MCTS | MCITP |

Backup Exec STS| Netbackup STS

mandar_khanolkar's picture

Earlier I could not see your attachement.

After looking at the error message, I can guess the problem. Please open your /etc/hosts file on your boot server. I guess there should be a first entry with boot server host name to 127.0.0.1 (i.e. localhost); which is not resolving host to network ip.

Please remove this entry and make sure correct ip-addr to boot server host name entry exists in this file.

Try doing "ping bs_hostname" from this same machine and it should show you correct network ip addr of your boot server and not 127.0.0.1

Try bmrsetupboot -register. It should work now.

Also there are some warning stating you do not have dhcp/tftp services configured on your boot server. These are required in case you intend to do nw based clietn recovery. For media based still it is ok not to have thsese services configured.

thanks.

mandar

Sacha Brown's picture

Hi Mandar,

 

Are you saying to remove the entry on the Windows mast server which is also the Windows boot server or on the Linux server that we would like to use as the Linux boot server. When looking at the hosts file on the Windows NBU Master server I did see the IP address 127.0.0.1. Im not too sure if it has to be removed there. Once this is clear I am confident in trying your suggestion.

 

You have to excuse me with this since I am not very familiar with Linux.

 

Thank you again.

 

Khamatee Brown

Systems Engineer 2

| MCP | MCTS | MCITP |

Backup Exec STS| Netbackup STS

mandar_khanolkar's picture

On Linux server that you would like to use as the Linux boot server where the attached error is coming while registering it using "bmrsetupboot -register".

And in case your Windows master has also similar then remove/comment it as well as it can give trouble later while resolving master host to ip.

Thanks.

mandar

Sacha Brown's picture

Thank You very much. One more thing before I try it. Can you list the path where the hosts file exists on a Linux server.

 

 

Khamatee Brown

Systems Engineer 2

| MCP | MCTS | MCITP |

Backup Exec STS| Netbackup STS

Sacha Brown's picture

Sorry..I just saw it in the earlier thread you sent /etc/hosts

 

 

 

 

Khamatee Brown

Systems Engineer 2

| MCP | MCTS | MCITP |

Backup Exec STS| Netbackup STS

Sacha Brown's picture

Hi Mandar,

I opened a case with Symantec before i created this post here. They finally did a webex and experienced the same error. I did not tyr what you recommended since the client wanted Symantec to resolve this issue. They claim that the tftp and dhcp services need to be configured. I told them that we only require media based client restore and not network and they they cannot work on this case because it is out of their scope.

 

I am a bit disappointed that I got this kind of response from Symantec.

 

Any suggestions?

 

 

 

Khamatee Brown

Systems Engineer 2

| MCP | MCTS | MCITP |

Backup Exec STS| Netbackup STS

mandar_khanolkar's picture

You definitely not require DHCP, TFTP and NFS services running in case you intend to do BMR media based restore. You can safely ignore WARNINGS during bmrsetup -register shown related to these services configuration.

You can take backup of etc/hosts file and try what i suggested. it will work.

If you dont mind please provide me the support case number for my reference.

Thanks.

mandar

Sacha Brown's picture

The case number is  03054400. Can you please send me your email address so I can send you the thread of emails sent by the assigned engineer.

 

My email address is khamatee.brown@icons-tt.com

Thank You

 

Khamatee Brown

Systems Engineer 2

| MCP | MCTS | MCITP |

Backup Exec STS| Netbackup STS

blanco.adalberto@ciime.mx's picture

Hi, everybody.

 

Maybe the problem is that probably when you settup the dhcp server you have created the dhcpd.conf file under /etc/dhcp/dhcpd.conf, so you can try creating a link to that file.

so:

ln -s /etc/dhcp/dhpd.conf /etc/dhcpd.conf

 

Because the /usr/openv/netbackup/bin/bmrsetupboot -register need that file in the /etc/dhcpd.conf location

 

Best regards.