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. Veritas NetBackup™ Deduplication Guide
  3. MSDP cloud support
  4. About the tool updates for cloud support
Veritas NetBackup™ Deduplication Guide

About the tool updates for cloud support

DCSCAN:

Dcscan downloads data container from the cloud. The default download path is <STORAGE>/tmp/DSID_#dsid, where #dsid is dependent on the cloud LSU DSID value. Different cloud storage providers have different DSID values. You do not need to know the DSID value, dcscan gets the DSID value automatically. The default download path can be modified in the contentrouter.cfg file using the DCSCANDownloadTmpPath field.

While using the dcscan tool to look at cloud data, -a option is disabled, because it downloads all data containers from cloud, it is an expensive operation. The -fixdo option is disabled as well, because dcscan only downloads data container from the cloud. Others operations are same as the local LSU.

SEEDUTIL:

Seedutil can be used for seeding a backup for a better deduplication rate. It creates links in the <destination client name> directory to all the backup files found in the path <client name>/<policy name> that have <backup ID> in their names. The user needs to know which DSID value the cloud LSU has used. That DSID value needs to be given to the seedutil, to let seedutil know which cloud LSU will seed a client. If you do a seeding for a local LSU, the default DSID is 2, you do not need to give the DSID value. Seedutil cannot seed across different DSIDs.

For example,/usr/openv/pdde/pdag/bin/seedutil -seed -sclient <source_client_name> -spolicy <source_policy_name> -dclient <destination_client_name> -dsid <dsid_value>.

CRCONTROL:

Using crcontrol - clouddsstat option to show cloud LSU datastore usage. DSID value needs to be given. As cloud storage has unlimited space, the size is hard-coded to 8 PB.

For example:

# /user/openv/pdde/pdcr/bin/crcontrol --clouddsstat <dsid_value>
************ Data Store statistics ************
Data storage      Raw    Size   Used   Avail  Use%
8.0P   											8.0P  	80.9G  8.0P   0%
Number of containers             : 3275
Average container size           : 26524635 bytes (25.30MB)
Space allocated for containers   : 86868179808 bytes (80.90GB)
Reserved space                   : 0 bytes (0.00B)
Reserved space percentage        : 0.0%

CRSTATS:

Using crstats -cloud -dsid option to show the cloud LSU statistics. DSID value needs to be given. As cloud storage has unlimited space, the size is hard-coded to 8 PB.

For example:

#/usr/openv/pdde/pdcr/bin/crstats --cloud-dsid <dsid_value>
Storage Pool Raw Size=9007199254740992Bytes
Storage Pool Reserved Space=0Bytes
Storage Pool Required Space=0Bytes
Storage Pool Size=9007199254740992Bytes
Storage Pool Used Space=86868179808Bytes
Storage Pool Available Space=9007112386561184Bytes
Catalog Logical Size=402826059439Bytes
Catalog files Count=3726
Space Allocated For Containers=86868179808Bytes
Deduplication Ratio=4.6

PDDECFG:

Using pddecfg to list all the cloud LSUs.

For example:

/usr/openv/pdde/pdcr/bin/pddecfg -a listcloudlsu
dsid, lsuname, storageId, CachePath
3, S3Volume, amazon_1/cloud-bucket1/sub1, /msdp/data/ds_3
4, S3Volume2, amazon_1/cloud-bucket1/sub2, /msdp/data/ds_4

Feedback

Was this page helpful?
Previous

About the configuration items in cloud.json, contentrouter.cfg and spa.cfg

Next

About the disaster recovery for cloud LSU

Feedback

Was this page helpful?