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™ Snapshot Manager for Data Center Administrator's Guide
  3. Preparing for NetBackup Snapshot Manager for Data Center installation
  4. Hosting NetBackup Snapshot Manager for Data Center
NetBackup™ Snapshot Manager for Data Center Administrator's Guide

Hosting NetBackup Snapshot Manager for Data Center

You can protect both cloud and on-premises assets using NetBackup Snapshot Manager for Data Center. To minimize costs and conserve network bandwidth, it is recommended to deploy NetBackup Snapshot Manager for Data Center in the same environment where you are protecting assets. To protect on-premises assets, deploy the NetBackup Snapshot Manager for Data Center host in the same on-premises environment. Likewise, to protect cloud assets, deploy it in the same cloud environment. This is not a limitation of Snapshot Manager for Data Center. You can protect cloud assets using an on-premises Snapshot Manager for Data Center, or protect on-premises assets using a cloud-deployed Snapshot Manager for Data Center.

You can deploy NetBackup Snapshot Manager for Data Center in a NetBackup media server, but not in a NetBackup primary server.

If you install NetBackup Snapshot Manager for Data Center on multiple hosts, we recommend that each NetBackup Snapshot Manager for Data Center instance manage separate resources. Two NetBackup Snapshot Manager for Data Center instances should not manage the same resources.

If you host the NetBackup Snapshot Manager for Data Center and media server in the same host, do the following for proper functioning of the backup from snapshot jobs:

  • Assign distinct IPs and NetBackup client names to the NetBackup Snapshot Manager for Data Center and the media server so that they can obtain different NetBackup Certificates. This is required to have different NetBackup host ID certificates for communication. Use the following configuration:

    • Configure the host with two network adapters.

    • Edit the /etc/hosts file and enter the details as mentioned in the following example:

      <IP Address MediaServer Host1>  < MediaServer Host1>
      <IP Address NetBackup Snapshot Manager for Data Center Host2>  <NetBackup Snapshot Manager for Data Center Host2>
    • Specify the MediaServer Host1 parameter in the /etc/hosts file during the Media server installation for the media server name.

    • Similarly select the NetBackup Snapshot Manager for Data Center Host 2 from the /etc/hosts file during the NetBackup Snapshot Manager for Data Center installation with a non-default port other than 443.

    • Start NetBackup Snapshot Manager for Data Center and Media services and register it with NetBackup primary server.

  • If the host name that you intend to use for NetBackup Snapshot Manager for Data Center is already mapped with a media server's host name, you must remove the older mapping. Refer to the Removing host ID to host name mappings section in the NetBackup Security and Encryption Guide.

  • Once the NetBackup Snapshot Manager for Data Center is registered, ensure that it has a different HOST DB entry.

  • Before performing the backup from snapshot jobs, perform the following optimization: DISABLE SHM and NOSHM. See: https://www.veritas.com/support/en_US/article.100016170

This ensures that NetBackup does not use shared memory to communicate among NetBackup data mover processes.

Feedback

Was this page helpful?
Previous

About the deployment approach

Next

Host sizing recommendations

Feedback

Was this page helpful?