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. Configuring and using universal shares
  4. About universal shares with object store
NetBackup™ Deduplication Guide

About universal shares with object store

Universal Shares with object store provides the ability for data in the universal shares to be directed to object storage in a deduplicated format.

Table:

Supported platforms

Description

Azure Kubernetes Service (AKS)

This platform is supported and enabled by default.

Amazon Elastic Kubernetes Service (EKS)

This platform is supported and enabled by default.

VM in Azure or AWS

This platform is supported. You must manually enable this option.

Note:

Ensure that you create a new copy of the auth.key file for each media server and or node on a separate computer when created and each time it is changed (Example: after a regular MSDP disaster recovery). The file is required to perform a universal share disaster recovery.

Lifecycle management of a universal share with object store

The three phases of the lifecycle management:

  • Create a universal share: Refer to the section Create a universal share in the NetBackup Web UI Administrator's Guide for more information about how to create a universal share.

  • Delete a universal share: If you delete the universal share in the NetBackup web UI, the MSDP cloud volume cannot be deleted if it is in use by any universal shares or instant access. If you delete a universal share, be aware that all of the snapshots from the universal share are expired on the local disk and the cloud bucket. You must log in to the media server to expire all the snapshot copies from the universal share before you delete it.

  • Snapshot retention and lifecycle: The vpfsd command runs a background thread and continues to monitor the retention of the snapshot copies. The vpfsd command expires the snapshot when the retention time is reached. The retention for the full snapshot and incremental snapshot can be configured in the vpfsd_config.json file.

More Information

Enabling a universal share with object store

Feedback

Was this page helpful?
Previous

Using the ingest mode to run a policy using NFS or SMB

Next

Enabling a universal share with object store

Feedback

Was this page helpful?