Ransomware attackers specifically target and attempt to destroy backup systems to increase the probability of payment. Hardening your system is critical. Please ensure you have reviewed your platform security using the Security Hardening Checklist
Cohesity

COHESITY Documentation

Explore our documentation to get started, discover products & new features, access troubleshooting guides, register sources, platforms support.

Products
Data Security Alliance
Visit Cohesity.com
Demos
Support
Blogs
Developers
Partner Portals
Cohesity Community
© 2026 Cohesity, Inc. All Rights Reserved.
Terms of Use|
Privacy Policy|
Legal|
  1. Home
  2. Veritas NetBackup™ for Hyper-V Administrator's Guide
  3. NetBackup Hyper-V for SCVMM
  4. Notes on NetBackup for Hyper-V with SCVMM
Veritas NetBackup™ for Hyper-V Administrator's Guide

Notes on NetBackup for Hyper-V with SCVMM

Note the following about NetBackup for Hyper-V with SCVMM:

  • Requires SCVMM 2012 R2 or later.

    For a list of supported versions of SCVMM, see the appropriate version of the NetBackup Software Compatibility List available from the following location:

    NetBackup Master Compatibility List

  • NetBackup client software must be installed on the SCVMM server and on each Hyper-V server.

  • Certain kinds of VMs are excluded from the backup list when the NetBackup Hyper-V policy runs:

    • Hyper-V VMs that are marked for deletion.

    • Hyper-V VM templates.

    • Hyper-V VMs that are stored on an SCVMM library server.

    • Any VMs that do not reside on a Hyper-V server, such as VMware VMs.

      Note:

      SCVMM can manage non-Hyper-V VMs. NetBackup for Hyper-V does not back up these VMs. To back up VMware VMs for example, use NetBackup for VMware.

    The Test Query dialog lists these types of VMs as Excluded, with a message that explains the reason for the exclusion. (The Test Query option is available on the policy Clients tab.)

  • Changes that are made through Hyper-V Manager on individual Hyper-V hosts or clusters can take up to 24 hours to be reflected in SCVMM. This delay is due to the Microsoft SCVMM refresh cycle. In an SCVMM environment, Microsoft recommends making VM configuration changes through SCVMM (not through the Hyper-V Manager on individual hosts or clusters). Changes that are made through the SCVMM Console are reflected immediately in SCVMM.

  • In an SCVMM environment, the VM GUID is referred to as the VM ID.

    Caution:

    If the SCVMM environment includes multiple VMs that have the same VM ID, each SCVMM refresh cycle reports only one of the VMs. Any other VM with the same VM ID is not visible. The NetBackup policy can back up only the VM that is currently reported or visible. Any other VM that has the same VM ID is not visible and is not backed up.

    To make sure that NetBackup can discover and back up all VMs, avoid duplicate VM IDs in the SCVMM environment.

  • To back up VMs in an SCVMM environment, the NetBackup policy must use queries to select the VMs automatically (Hyper-V Intelligent Policy). If the query includes localized (non-English) values, the policy may not be able to select and back up the VMs.

    See Creating a query to back up VMs in a localized SCVMM environment.

Feedback

Was this page helpful?
Previous

About backup of virtual machines in an SCVMM environment

Next

Creating a query to back up VMs in a localized SCVMM environment

Feedback

Was this page helpful?