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. NetBackup™ Deduplication Guide
  3. MSDP volume group (MVG)
  4. Configuring the MSDP volume group
  5. MSDP volume group requirements
NetBackup™ Deduplication Guide

MSDP volume group requirements

The requirements for an MVG server:

  • An MVG server can run on any NetBackup media server on the Red Hat Enterprise Linux platform.

    • It can be a Flex media server container, a BYO media server, or a primary server.

    • It is recommended that you run an MVG server on a Flex multi-node appliance or along with the NetBackup primary server.

      See About MVG resilience.

    • It is not an MSDP container like that on Flex WORM, Access Appliance, NetBackup Flex Scale, or Cloud Scale.

    • An MVG server and MSDP server cannot exist on the same media server as an MVG server is a lightweight MSDP server.

  • As the MVG server is new, it cannot be upgraded or migrated from a regular MSDP server.

  • By default, one MVG server can have up to 64 MVG volumes, and each MVG volume can have up to 8 disk volumes.

  • The disk volumes PureDiskVolume or cloud volumes cannot be configured on an MVG server.

  • The MVG server requires hundreds of gigabytes of disk storage in a large environment.

  • One NetBackup domain can have multiple MVG servers.

The requirements for the disk volumes of an MVG volume:

  • The MSDP servers of the disk volumes must run with NetBackup 10.5 or later.

  • The MVG server can use its default credentials to access the MSDP servers of the disk volumes.

  • The disk volumes must be all PureDiskVolumes or all cloud volumes.

  • The disk volumes must come from different MSDP servers.

  • The disk volumes must have the same KMS, encryption, and WORM settings.

  • If they are cloud volumes, they should be configured with comparative storage classes or tiers.

  • The WORM MVG volumes must have overlapping ranges for retention locks. Within the WORM MVG volume, the shortest maximum lock duration for any WORM volume must be greater than the longest minimum lock duration for any WORM volume.

    See Examples of valid WORM MVG volumes.

  • A disk volume cannot be assigned to multiple MVG volumes.

Feedback

Was this page helpful?
Previous

Configuring the MSDP volume group

Next

Configuring an MVG server using the web UI

Feedback

Was this page helpful?