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™ for Kubernetes Administrator's Guide
  3. Deploying and configuring the NetBackup Kubernetes operator
  4. Customize Kubernetes workload
  5. Customization of datamover properties
NetBackup™ for Kubernetes Administrator's Guide

Customization of datamover properties

You can customize datamover properties by passing key-value pairs in the backup server specific configmap.

Table: Datamover properties

Key Name

Possible Values

VXMS_VERBOSE

Range:[0,99]

VERBOSE

Range:[0,5]

DTE_CLIENT_MODE

  • AUTOMATIC

  • ON

  • OFF

USE_CTIME_FOR_INCREMENTALS

YES / NO

USE_CTIME_FOR_DIRECTORY_INCRS

YES / NO

DO_NOT_RESET_FILE_ACCESS_TIME

YES / NO

Note:

Any other configuration setting that is supported by NetBackup client can be set for datamover by adding it under datamover.properties key in the datamover configmap. These configurations will be added in bp.conf file inside the datamover.

To update the configmap, add the key value pairs as follows:

apiVersion: v1
data:
  datamover.properties: |
        image=reg.domain.com/datamover/image:latest
        VERBOSE=5
        DTE_CLIENT_MODE=OFF
        VXMS_VERBOSE=5
  version: "1"
kind: ConfigMap
metadata:
  name: backupserver.sample.domain.com
  namespace: kops-ns

Starting with NetBackup 10.5, TLS 1.3 protocol is supported. NetBackup 10.5 and later versions use TLS 1.3 protocol by default in secure communication workflows as follows:

  • secure proxy

  • data-in-transit encryption (DTE)

  • external KMS server

  • AD/LDAP server

  • MSDP

  • HTTPS communication using cURL

To configure TLS related properties, the required settings can be updated in this configmap. For more details about TLS settings refer the article.

Feedback

Was this page helpful?
Previous

DTE client settings supported in Kubernetes

Next

Troubleshooting NetBackup servers with short names

Feedback

Was this page helpful?