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™ Deployment Guide for Azure Kubernetes Services (AKS) Cluster
  3. Managing MSDP Scaleout
  4. About MSDP Scaleout logging and troubleshooting
  5. Collecting the logs and the inspection information
NetBackup™ Deployment Guide for Azure Kubernetes Services (AKS) Cluster

Collecting the logs and the inspection information

You can collect the logs and inspection information for MSDP Scaleout for troubleshooting purpose.

Run the command kubectl msdp collect-logs

For example, kubectl msdp collect-logs -o <output path> [-n <MSDP operator namespace>] [-c <MSDP applications namespace(s)>]

Table: collect-logs command options

Option

Description

-c

Comma-separated namespaces of MSDP applications.

Note:

If not specified, it collects MSDP applications of all namespaces.

-f

Output format of logs/core files/MSDP history files.

Available options:

targz: Copy logs/core files/MSDP history files from containers and compress them by tar/gzip.

raw: Copy logs/core files/MSDP history files from containers as same format in the containers.

Default value: targz

-n

Namespace of MSDP operator.

Default value: msdp-operator-system

-o

Output path of the log file.

Feedback

Was this page helpful?
Previous

About MSDP Scaleout logging and troubleshooting

Next

About MSDP Scaleout maintenance

Feedback

Was this page helpful?