BMR for Solaris 11 in Virtual machine LDOM failed

[enguessan]

Hello all,

I'm trying to make BRM on Oracle VM LDOM for Solaris 11.

I have the following error saying that there is no /cdrom.

cdrom on ldom is mount as disk on /.cdrom

bellow the message.

can someone help me resolv that issue?

Enter the NetBackup client name : client
Enter the client's netmask (dotted decimal form) : 192.168.200.8

Enter the client's netmask (dotted decimal form) : 255.255.255.0
Enter the NetBackup master server name : master
Enter the NetBackup master server IP Address (dotted decimal form) : 192.168.200.1
Enter the client's default gateway (dotted decimal form) : 192.168.200.250
add net default: gateway 192.168.2.250
add persistent net default: gateway 192.168.2.250
Hostname: client
Apr 21 17:42:33 netbackup[1353]: OID:122:V-1-6 Unable to load configuration settings.
Apr 21 17:42:33 netbackup[1353]: OID:128:V-1-6 Unable to load configuration settings.
Apr 21 17:42:35 netbackup[1420]: OID:122:V-1-6 Unable to load configuration settings.
Apr 21 17:42:35 netbackup[1420]: OID:128:V-1-6 Unable to load configuration settings.
Apr 21 17:42:35 netbackup[1423]: OID:122:V-1-6 Unable to load configuration settings.
Apr 21 17:42:35 netbackup[1423]: OID:128:V-1-6 Unable to load configuration settings.
Apr 21 17:42:35 netbackup[1426]: OID:122:V-1-6 Unable to load configuration settings.
Apr 21 17:42:35 netbackup[1426]: OID:128:V-1-6 Unable to load configuration settings.
Apr 21 17:42:35 netbackup[1429]: OID:122:V-1-6 Unable to load configuration settings.
Apr 21 17:42:35 netbackup[1429]: OID:128:V-1-6 Unable to load configuration settings.
Reconfiguring /dev and /devices for Bare Metal Restore
Apr 21 17:42:37 netbackup[1439]: OID:122:V-1-6 Unable to load configuration settings.
Apr 21 17:42:37 netbackup[1439]: OID:128:V-1-6 Unable to load configuration settings.
Apr 21 17:42:37 netbackup[1442]: OID:122:V-1-6 Unable to load configuration settings.
Apr 21 17:42:37 netbackup[1442]: OID:128:V-1-6 Unable to load configuration settings.
Apr 21 17:42:38 netbackup[1446]: OID:122:V-1-6 Unable to load configuration settings.
Apr 21 17:42:38 netbackup[1446]: OID:128:V-1-6 Unable to load configuration settings.
ERROR: Shared Resource Tree /cdrom/ not mounted.
ERROR: Please boot with correct Media Boot CD or network boot image.
Apr 21 17:42:38 netbackup[1450]: OID:122:V-1-6 Unable to load configuration settings.
Apr 21 17:42:38 netbackup[1450]: OID:128:V-1-6 Unable to load configuration settings.
Apr 21 17:42:38 netbackup[1456]: OID:122:V-1-6 Unable to load configuration settings.
Apr 21 17:42:38 netbackup[1456]: OID:128:V-1-6 Unable to load configuration settings.

Bare Metal Restore has failed.
Now, you will be dropped to a shell prompt.
You may reboot the system when you have completed diagnosis.

 df -h
Filesystem             Size   Used  Available Capacity  Mounted on
/devices/ramdisk-root:a
                       233M   142M        91M    62%    /
/devices                 0K     0K         0K     0%    /devices
/dev                     0K     0K         0K     0%    /dev
ctfs                     0K     0K         0K     0%    /system/contract
proc                     0K     0K         0K     0%    /proc
mnttab                   0K     0K         0K     0%    /etc/mnttab
swap                   5.3G   2.0M       5.3G     1%    /system/volatile
objfs                    0K     0K         0K     0%    /system/object
sharefs                  0K     0K         0K     0%    /etc/dfs/sharetab
/devices/virtual-devices@100/channel-devices@200/disk@0:a
                       630M   630M         0K   100%    /.cdrom
/dev/lofi/1            1.1G   1.1G         0K   100%    /usr
/dev/lofi/2            105M   105M         0K   100%    /mnt/misc
/mnt/misc/opt          105M   105M         0K   100%    /mnt/misc/opt
swap                   5.3G    16K       5.3G     1%    /root
swap                   5.3G    64K       5.3G     1%    /jack
swap                   5.3G   280K       5.3G     1%    /tmp

[enguessan]

that artical is not available on Symantec Site.

[enguessan]

can some nody help me have the below Tech. there is no way to get it on symantec web site

http://www.symantec.com/docs/TECH54765

[CRZ]

Looks like it was unpublished - I've republished it.

[Jaime_Vazquez]

I updated the article and republished for external viewing. Hope it helps.

[enguessan]

Hi Vazquez,

In attached the proof of restoring LDOM Solaris10 with ZFS filesystem.

for the net boot of solaris11, I already have the same message :

[root@srvnetbackup openv]# bmrprep -restore -client sol11test02 -config restore -srt srtsol11sparc -logging
V-128-749 Operation failed due to network problem.
[Error] V-126-53 Could not contact the Bare Metal Restore Boot Server daemon (bmrbd)
on host 'sol11test01'.
Make sure that the host is reachable and that the daemon is running,
and retry the operation.
[Error] V-126-3 'bmrprep' could not complete the requested operation.
Please see logs for additional information.
[Info] V-126-43 Cleaning up. Please wait...
[root@srvnetbackup openv]#
 

BR

[enguessan]

Hi Vazquez,

I well received the TECH.

but I have the same error on solaris 11

[root@srvnetbackup openv]# bmrprep -restore -client sol11test02 -config restore -srt srtsol11sparc -logging
V-128-749 Operation failed due to network problem.
[Error] V-126-53 Could not contact the Bare Metal Restore Boot Server daemon (bmrbd)
on host 'sol11test01'.
Make sure that the host is reachable and that the daemon is running,
and retry the operation.
[Error] V-126-3 'bmrprep' could not complete the requested operation.
Please see logs for additional information.
[Info] V-126-43 Cleaning up. Please wait...
[root@srvnetbackup openv]#

But on solaris 10, the bmrprep works

[root@srvnetbackup openv]# bmrprep -restore -client sol10test02 -config current -srt srtsol10sparc -logging
[Info] V-126-11 BMR client 'sol10test02' is ready to be restored. Please boot the client to proceed.
[root@srvnetbackup openv]#
 

Is there any solution?

BR
 

[Jaime_Vazquez]

The "bmrprep" process logs to the unified log id of 126 on the Master Server.
It logs to the 119 id on the Boot Server for the "bmrbd" process.

Set the "DebugLevel" for each to 5 to get sufficiently detailed information for diagnostic assistance. Use the "vxlogview" command to display the debug information.

The previous problem was associated with a restore time error in the restore script. The "bmrprep" ran to completion with no problem.  When using a media based SRT, the BMR Boot Server is not contacted as part of the activity.

When using a network based SRT, all of the actions and processes noted in the TECH article come into play.

BMR Boot Servers can  be listed on the Master, using "bmrs -o list -res BootServer". In the output of that command, for each entry, the last column is the server ID number. You can display details of this server by running:

bmrs -o querytree -res database -table BootServer -id $SERVER_ID_NUMBER

This will display all details of the server and of all SRT instances the BMR Master knows about.

This failure is fairly early on.  The "bmrprep" program will need to contact the "bmrbd" daemon on the noted Boot Server (sol11test01) to perform the network boot setup needed. To help verify this, log on to the Boot Server and run the command "bmrsrtadm".  The initial setup will contact the Master Server to ensure it is running and then display a selection menu. If the "bmrbd" daemon is not running or it cannot contact the Master, this will fail. Make sure host name to IP resolution is correct both ways.

BMR Boot Server will register to the  Master Server that supports it by the name it is registered with. Verify this by running the command "bpclntcmd -pn".  This should display the name of the Master Server for the system ("expecting response from ...") and the client name of requesting system, as seen by the Master Server.

Verify the settings noted above and see if you can repair this environment.

[enguessan]

Hello All,

I found the solution for restoraing Solaris 11 on LDOM environnement.

In attached the Procedure I made.

BR