Veritas NetBackup™ Deduplication Guide
- Introducing the NetBackup media server deduplication option
- Planning your deployment
- About MSDP storage and connectivity requirements
- About NetBackup media server deduplication
- About NetBackup Client Direct deduplication
- About MSDP remote office client deduplication
- About MSDP performance
- MSDP deployment best practices
- Provisioning the storage
- Licensing deduplication
- Configuring deduplication
- Configuring the Deduplication Multi-Threaded Agent behavior
- Configuring the MSDP fingerprint cache behavior
- Configuring MSDP fingerprint cache seeding on the storage server
- Configuring a storage server for a Media Server Deduplication Pool
- Configuring a disk pool for deduplication
- Configuring a Media Server Deduplication Pool storage unit
- About MSDP optimized duplication within the same domain
- Configuring MSDP optimized duplication within the same NetBackup domain
- Configuring MSDP replication to a different NetBackup domain
- About NetBackup Auto Image Replication
- Configuring a target for MSDP replication to a remote domain
- Creating a storage lifecycle policy
- Resilient Network properties
- Editing the MSDP pd.conf file
- About protecting the MSDP catalog
- Configuring an MSDP catalog backup
- Configuring deduplication to the cloud with NetBackup CloudCatalyst
- Using NetBackup CloudCatalyst to upload deduplicated data to the cloud
- Configuring a CloudCatalyst storage server for deduplication to the cloud
- Monitoring deduplication activity
- Viewing MSDP job details
- Managing deduplication
- Managing MSDP servers
- Managing NetBackup Deduplication Engine credentials
- Managing Media Server Deduplication Pools
- Changing a Media Server Deduplication Pool properties
- Configuring MSDP data integrity checking behavior
- About MSDP storage rebasing
- Managing MSDP servers
- Recovering MSDP
- Replacing MSDP hosts
- Uninstalling MSDP
- Deduplication architecture
- About unified logging
- About legacy logging
- Troubleshooting MSDP installation issues
- Troubleshooting MSDP configuration issues
- Troubleshooting MSDP operational issues
- Troubleshooting CloudCatalyst issues
- CloudCatalyst logs
- Problems encountered while using the Cloud Storage Server Configuration Wizard
- Disk pool problems
- Problems during cloud storage server configuration
- CloudCatalyst troubleshooting tools
- Appendix A. Migrating to MSDP storage
esfs_check consistency checking tool
The esfs_check tool determines whether the data that is stored in the cloud and the data in the ESFS database are consistent, and then reports any inconsistencies between the two.
Since the tool reads data from the cloud, it is likely that the NetBackup customer will incur a financial cost by the cloud vendor. Consider contacting Veritas Support before running the tool.
The esfs_check tool is located in the following directory: /usr/openv/esfs/bin
It uses the following syntax:
esfs_check -cachedir path_to_local_cache [-strict] [-verbose]
path_to_local_cache is the path to the local cache directory.
The -strict option provides an additional check to compare the file size in the local cache with the file size in the ESFS database.
The -verbose option enables logging to the following directory:
Before running the esfs_check tool:
The following example output shows that the data that is stored in the cloud is consistent with the ESFS database.
esfs_check -cachedir /root/cache/msdp/ -verbose consistency check successful
The following example output shows that there are inconsistencies between the cloud and the ESFS database.
esfs_check -cachedir /root/cache/msdp/ -verbose File /data/2/97.bin not exist in cloud, expect in cloud File /data/2/97.bin not exist in cache/cloud
Output line 1 means that file /data/2/97.bin appears in the ESFS database and should also be in the cloud, but it is not.
Output line 2 means that file /data/2/97.bin appears in the ESFS database, but is neither in the cloud nor the local cache.
If the esfs_check tool finds an inconsistency, contact Veritas Support.