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™ Security and Encryption Guide
  3. Section III. Encryption of data at rest
  4. Data at rest encryption security
  5. Configuring legacy encryption on clients
  6. About configuring legacy encryption from the server
NetBackup™ Security and Encryption Guide

About configuring legacy encryption from the server

You can configure most NetBackup clients for encryption by using the bpinst command from the server.

Prerequisites for this method include the following:

  • The NetBackup client software must be running on a platform that supports NetBackup encryption.

    Refer to the NetBackup Release Notes for details on supported platforms.

  • The NetBackup clients must be running the required NetBackup version.

  • If a clustered server is a client for NetBackup encryption, ensure that all nodes in the cluster have the same key file.

The bpinst command is loaded into the NetBackup bin directory on the server as follows:

  • For a Windows server, the bin directory is as follows

    install_path\NetBackup\bin
  • For a UNIX server, the bin directory is as follows

    /usr/openv/netbackup/bin

See the bpinst command description in the NetBackup Commands Reference Guide for details about the options that are available with the bpinst command.

For examples about how to use bpinst:

See About pushing the legacy encryption configuration to clients.

See About pushing the legacy encryption pass phrases to clients.

Normally, you specify client names in the bpinst command. However, if you include the -policy_names option, you specify policy names instead. The option affects all clients in the specified policies.

Feedback

Was this page helpful?
Previous

Managing legacy encryption key files

Next

About pushing the legacy encryption configuration to clients

Feedback

Was this page helpful?