That's all very well Sajeev but if your VLAN infrastructure does not allow for the use of nbd as a transport type - what are the alternatives? Is there going to be an EEB appearing soon? I have exactly this problem on NB 7.5.0.3.

in my case this was the solution. What exactly is the error message? Your restored VMs dont boot up ?

Sajeev - I sent you a message but I thought I should reproduce it here in case it helps others .

Hi Sajeev - thanks for replying. We have a small number of Shared Storage Media Servers. The Master server is AIX 6.1 as are another 4. We also have a VMware infrastructure and a VMware media server (Windows Server 2008R2) handling the backups via the VCentre. We have recently upgraded to NB 7.5.0.3. We experienced the fault with VMware backups as described in http://www.symantec.com/business/support/index?page=content&id=TECH191198 , applied the fix and backups via SAN then worked as before (we upgraded from 7.5.0.1). Restores via SAN also worked. However, when attempting to boot the restored container (Windows & Linux) we get the message "No Operating System Found" as described in

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2021483.

VMware details :-

VMware vCentre version: 5.0.0, 623373 (vsphere 5.0 update1)

VMware hosts version:  ESXi 5.0.0, 623860  (vsphere 5.0 update1)

Datastore Version: VMFS-5

Our LAN infrastructure does not allow us to use NBD but I am going to try and see if I can get the appropriate ports opened to see if the restored container will boot.

Having messed around with our network I can now backup and restore via LAN OK. The good news is that the restored VM does indeed boot so I can confirm that your workaround does work in my case as well.

It is however only a workaround and I will now log this with Symantec - assuming the MySupport website is up today.

the other option is to use the OS install CD/DVD and repair the boot partition. Works for Windows and Linux.