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
- About MSDP stream handlers
- 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
- About MSDP Encryption using NetBackup KMS service
- 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
- About NetBackup WORM storage support for immutable and indelible data
- Configuring deduplication to the cloud with NetBackup Cloud Catalyst
- Using NetBackup Cloud Catalyst to upload deduplicated data to the cloud
- Configuring a Cloud Catalyst storage server for deduplication to the cloud
- MSDP cloud support
- About MSDP cloud support
- 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
- Troubleshooting
- About unified logging
- About legacy logging
- Troubleshooting MSDP installation issues
- Troubleshooting MSDP configuration issues
- Troubleshooting MSDP operational issues
- Troubleshooting Cloud Catalyst issues
- Cloud Catalyst logs
- Problems encountered while using the Cloud Storage Server Configuration Wizard
- Disk pool problems
- Problems during cloud storage server configuration
- Cloud Catalyst troubleshooting tools
- Trouble shooting multi-domain issues
- Appendix A. Migrating to MSDP storage
Oracle stream handler
The Oracle stream handler is enabled by default for newly created Oracle policies after an upgrade to NetBackup 8.3. By default, the Oracle stream handler only supports stream-based backups. You can enable and disable the Oracle stream handler per policy or all policies at once using the cacontrol command line utility.
When the Oracle stream handler is used, the FILESPERSET variable is more flexible. You can set FILESPERSET > 1 in the policy or the bp.conf
without a large decrease in deduplication rates.
The Marker Entry
file is used to override the default behavior by using the cacontrol command utility with the --sth flag at a client and or policy level only.
Note:
When you use the Oracle stream handler, it is not recommended to use variable-length deduplication.
Update a Marker Entry
policy by using the following cacontrol options:
You can create and or update a
Marker Entry
policy.cacontrol --sth update <STHTYPE> <CLIENT> <POLICY> [SPAUSER] <enabled | disabled>
You can query the setting for the stream handler per policy.
cacontrol --sth get <STHTYPE> <CLIENT> <POLICY> [SPAUSER]
You can delete the settings to use the default behavior.
cacontrol --sth delete <STHTYPE> <CLIENT> <POLICY> [SPAUSER]