Am I missing something or is NetBackup way behind in Hyper-V support compared to VMWare. We have a VMWare and a Hyper-V implementation and we have replication for both for DR purposes (SRM for the one and native hyper-v replication for the other). Why is NetBackup smart enough not to backup the VMWare placeholder templates (replication placeholders) at the target site and still pull in the actually running VMs at that site, but it's not smart enough to do the same for Hyper-V replicated VMs. Instead, it will go ahead and backup all of the VMs on the host being backed up, regardless of whether they are actually the powered off DR target of a replicated production VM on another host.
Also, for VMWare, Netbackup is smart enough to find the right vCenter that is managing a VM and back it up, regardless of the host it is on. It does this by us having the vCenter creds created outside of the policy - you merely use those creds implicitly when you edit a policy and browse for the VMs to backup.
Why couldn't the same thing be done for Hyper-V? As it stands, I have to have separate policies now to backup each VM that is effectively managed through a different Hyper-V since the Hyper-V itself is tied to a specific policy. Now I know everyone is going to say, just backup the replicated copy and call it good, but it's not good. I want a fully quiesced copy of the VM at the current production site being backed up, not the replicated copy that I'm not quite fully sure of the current state (and can't be, because it's POWERED OFF). Safer to make the backup of the currently running VM...
Lot's of questions, hopefully someone can respond since I don't see any documented strategy from Symantec on the backup of Hyper-V in a replicated DR scenario, relative to how it is done for the VMWare counterpart...