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. MSDP cloud support
  4. Cloud space reclamation
  5. Configuring the cloud compaction
NetBackup™ Deduplication Guide

Configuring the cloud compaction

Cloud compaction replaces the existing container with the garbage with a new smaller container without the garbage. It is similar to compaction for local storage. In the compaction process, containers that meet the conditions are downloaded from object cloud storage to local copies. Compaction removes garbage in the local copies and uploads them to overwrite the old objects in the cloud. In this process, data is transferred to and from cloud storage and may incur extra cost. It also needs reasonable bandwidth for compaction to work efficiently. Hence, cloud compaction is disabled by default. It can be enabled in the deployment where cost and bandwidth are not a problem. For example, it's recommended to enable it in a private cloud or in case MSDP is deployed in the same cloud as object storage.

Limitations:

  • WORM cloud LSU is not supported.

  • Buckets with versioning enabled are not supported.

  • CloudCatalyst migration system is not supported.

  • MSDP Cluster deployments (AKS, EKS, NBFS) are not supported.

You can configure cloud compaction with the following options in cloud.json

Parameter

Description

Default value

CompactEnable

Enable or disable cloud compaction.

false

CompactBatchNum

The number of containers for cloud compaction each time.

400

EnableCompactCandidateCheck

Enable or disable cloud compaction check. This value is available when CompactEnable is true.

true

CompactLboundMB

Filter the containers that have garbage size less than this value for cloud compaction.

16

CompactSizeLboundMB

Filter the containers with the size less than this value for cloud compaction.

32

CompactMaxPo

Filter the containers that are referenced more than this number of path objects for cloud compaction.

100

To update the cloud compaction parameters using crcontrol command line

  1. Enable cloud compaction for one cloud LSU.

    /usr/openv/pdde/pdcr/bin/crcontrol --cloudcompacton <dsid>

    This command enables compaction temporarily. To enable compaction permanently, update CompactEnable value manually in cloud.json.

    Container aging is disabled automatically when cloud compaction is enabled.

  2. Disable cloud compaction for one cloud LSU.

    /usr/openv/pdde/pdcr/bin/crcontrol --cloudcompactoff <dsid>

    To disable compaction permanently, update CompactEnable manually in cloud.json, and restart spoold.

  3. Show cloud compaction state for all cloud LSUs.

    /usr/openv/pdde/pdcr/bin/crcontrol --cloudcompactstate

Feedback

Was this page helpful?
Previous

Configuring the container aging

Next

About the tool updates for cloud support

Feedback

Was this page helpful?