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. Configuring and managing universal shares
  4. Troubleshooting issues related to universal shares
  5. Data integrity check and recovery using the vpfsd service
NetBackup™ Deduplication Guide

Data integrity check and recovery using the vpfsd service

The vpfsd service performs a data integrity check in the background according to the data changes. An event is sent to the NetBackup primary when file corruption is detected, which includes the metadata and the data corruption (automatic process).

The corrupted file is moved to the following location:

/mnt/vpfs_share/<share dir>/<share ID>/.vpfs_corrupted

A syslog and a history log are created for the file. The backup of the universal share skips the files that have an issue.

Apart from the automatic process, you can use the vpfsck command to manually verify and detect the file corruption, and the corrupted file is moved to the following location:

/mnt/vpfs_share/<share dir>/<share ID>/.vpfs_corrupted

Only local VPFS is supported.

For example:

--verify_data  --share_id <share id> 
 [--t <file creation time older than (int) hours>]
 --check_so    --share_id <share id> 
 [--so <so fp, find files that contain this so>] 
 [--file_path <check single file or folder, 
 path relative to /mnt/vpfs/<share_id<0:4>>/<share_id>>]
 --verbose  optional

All the options after --share_id are optional.

The process is logged at <storage>/log/vpfs/vpfsd/vpfsck.log and the option --verbose enables the debug log for vpfsck.

Feedback

Was this page helpful?
Previous

Notify events to primary server with the vpfsd service

Next

Configuring isolated recovery environment (IRE)

Feedback

Was this page helpful?