Master - NB52x0 - v2.6.0.2 - and the MSDP storage contains a full backup of client named 'winclient7602'.
ESX - vSphere v5.5 (base - no patches)
Media - Win2008 R2 SP1 - NBU v7.6.0.2 Enterprise Server
Client - Win2008 R2 SP1 - NBU v7.6.0.2 Client
I understand that to B2V a Windows backup to create a Windows VM, one needs a Windows based VIC (Virtual Image/Instance Converter):
http://www.symantec.com/business/support/index?pag...
...so I created a Windows 2008 R2 SP1 media server running NBU 7.6.0.2.
The full BMR based backup image of winclient7602 is within the MSDP storage on the master server appliance.
I've added host 'media7602' as VMware Access Host on master server properties.
And added media7602 to teh Storage Server credentials of 'master2602a PureDisk'.
(I have been able to backup a separate VM from the ESX hosts, so I know that's working.)
Re-started NetBackup processes on master.
When I try a B2V, I get:
...but the catalog definitely contains an original full image:
master2602a:/home/maintenance # bpimagelist -client winclient7602 -U -d 01/01/1970 00:00:00 Backed Up Expires Files KB C Sched Type On Hold Index Status Policy ---------------- ---------- -------- -------- - --------------- ------- ------------ ------------ 22/08/2014 11:53 05/09/2014 7731 4358832 N Full Backup 0 0 POL-TEST01 22/08/2014 11:41 05/09/2014 15842 10597004 N Full Backup 0 0 POL-TEST01
Does the VIC host (media7602) have to own the backup image, or have the image directly accessible within its own storage?
Any obvious tips before I start delving through logs?