The NetBackup doc re support for virtual encironments was updated yesterday (7th May 2014), and now includes additional statements surrounding Win2012 R2 Hyper-V and NetBackup v184.108.40.206:
Adds support for Microsoft Hyper-V Server 2012 R2. Also adds support for VHDX files.
NetBackup limitations on Hyper-V Server 2012 and Hyper-V Server 2012 R2:
Block-level incremental backup is not supported.
File-level recovery from a Hyper-V backup is not supported in any of the following cases:
The files inside a VM reside in a Resilient File System (ReFS) volume.
The files inside a VM reside in an NTFS deduplicated volume.
The files are in a VM (any guest OS) that resides on a Hyper-V 2012 R2 server with the Windows Server 2012 R2 update of April 2014.
For more information on the update, see the following Microsoft article:
Apart from the above restrictions, file-level recovery is supported when the files inside the
VM reside in an NTFS volume and the VM is composed of VHD or VHDX files.
...but, the MS KB article:
Important All future security and nonsecurity updates for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 require this update to be installed. We recommend that you install this update on your Windows RT 8.1, Windows 8.1, or Windows Server 2012 R2-based computer in order to receive continued future updates.
Does anyone in Symantec know whether an EEB, to workaround this restriction for NBU v220.127.116.11, will be issued soon ?
Solved! Go to Solution.
Argh, we've been waiting for this patch for months, only to have Lucy snatch the football away as we're about to kick it with this lack of support for the OS Update... Please tell me we aren't waiting until 18.104.22.168 for this, and it's just a matter of completing the testing process...
This is an unfortunate timing issue between NetBackup release update and Windows update. By the time 22.214.171.124 was ready to ship, we had also taken additional efforts to validate this recent Windows update (April 2014) and found that granular recovery needs additional changes to support the new Windows update. Instead of delaying 126.96.36.199 further (as you guys already know it was needed in the field for a number of good reasons), we shipped it with that note.
An EEB is being developed to address this. We will have an idea on ETA once the scope of changes is estimated.