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. About MSDP lazy delete
NetBackup™ Deduplication Guide

About MSDP lazy delete

MSDP lazy delete lets you retain the uploaded data to the cloud for the failed jobs for a certain period. This allows the retrying jobs to reference the already successfully uploaded data, reducing data duplication, improving efficiency, and lowering storage costs. For example, if 80% of the data was uploaded before a failure, the retried job uses that 80% and uploads only the remaining 20%. This feature is especially useful with the archive tiers like AWS Glacier or Azure Archive, which have minimum retention requirements.

The MSDP lazy delete is enabled by default. It retains the metadata of failed jobs for 2 days by default. You can update it or disable it by using the msdpcldutil lazy-delete command. For more information about the command usage, see the NetBackup Commands Reference Guide.

When MSDP lazy delete is disabled, NetBackup image cleanup removes the fragments of the image uploaded to the cloud. The MSDP does not use the unique data of a deleted image even if the data is still stored in the object storage. When the job is run again, it stores the same data in the cloud again. The duplicate data increases in object storage with each retried job.

Feedback

Was this page helpful?
Previous

Configuring the cloud direct for restore

Next

About verification of the images stored in the archive tier

Feedback

Was this page helpful?