NetBackup™ Deduplication Guide
- Introducing the NetBackup media server deduplication option
- Quick start
- 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
- MSDP cloud support
- About MSDP cloud support
- About the disaster recovery for cloud LSU
- About Image Sharing using MSDP cloud
- About MSDP cloud immutable (WORM) storage 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
- Configuring and using universal shares
- Troubleshooting
- About unified logging
- About legacy logging
- Troubleshooting MSDP installation issues
- Troubleshooting MSDP configuration issues
- Troubleshooting MSDP operational issues
- Trouble shooting multi-domain issues
- Appendix A. Migrating to MSDP storage
- Appendix B. Migrating from Cloud Catalyst to MSDP direct cloud tiering
- About direct migration from Cloud Catalyst to MSDP direct cloud tiering
- Appendix C. Encryption Crawler
Oracle stream handler
The Oracle stream handler is not enabled by default for existing and new Oracle clients in NetBackup 8.3. Also, the Oracle stream handler only supports stream-based backups and you can enable and disable the Oracle stream handler per <client> <policy> combination using the cacontrol command line utility.
In NetBackup 10.0, the Oracle stream handler is enabled (by default) for all new clients that have no existing images. As with previous versions, the Oracle stream handler only supports stream-based backups and you can configure the Oracle stream handler using the cacontrol command line utility. You can enable and disable the stream handler per the following:
Policy and client
Policy level
Stream type level
Note:
When you use the Oracle stream handler, it is not recommended to use variable-length deduplication.
The cacontrol command utility with the --sth flag, is used to override the default behavior of NetBackup by creating a Marker Entry
for a client, policy, or stream type in a configuration file. The cacontrol command utility is located in the following locations:
Windows:
install_path\Veritas\pdde\cacontrol
UNIX:
/usr/openv/pdde/pdcr/bin/cacontrol
In the following examples for cacontrol, STHTYPE must be set to Oracle to configure the Oracle stream handler.
In NetBackup 8.3, you can configure cacontrol using the following options:
You can query the settings for the stream handler per client and policy.
cacontrol --sth get <STHTYPE> <CLIENT> <POLICY> [SPAUSER]
You can enable the stream handler per client and policy.
cacontrol --sth update <STHTYPE> <CLIENT> <POLICY> [SPAUSER] <enabled>
You can delete the settings for client and policy (return to default behavior).
cacontrol --sth delete <STHTYPE> <CLIENT> <POLICY> [SPAUSER]
You can disable the stream handler on a client and policy.
cacontrol --sth update <STHTYPE> <CLIENT> <POLICY> [SPAUSER] <disabled>
Note:
When you use cacontrol to set <POLICY> or <STHTYPE> to enabled, NetBackup enables all the old clients which have existing images. The deduplication rate decreases significantly only at the first backup after enabled. Also, the storage usage increases only in the first backup after enabled. Basically, NetBackup behaves as if you have run a first full backup. Both the deduplication rate and storage usage improve after initial activation of the stream handler.
When using the cacontrol command utility to create a Marker Entry
in NetBackup 10.0, priority is given to the more granular configuration. For example:
Marker Entry 1: <Client1> <Policy1> to enabled
Marker Entry 2: <Policy1> to disabled
The stream handler is enabled because the more granular configuration in Marker Entry 1
has higher priority.
In NetBackup 10.0, you can configure cacontrol using the following options:
You can query the settings for the stream handler per client and policy.
cacontrol --sth get <STHTYPE> <CLIENT> <POLICY> [SPAUSER]
You can enable the stream handler per client and policy.
cacontrol --sth update <STHTYPE> <CLIENT> <POLICY> [SPAUSER] <enabled>
You can delete the settings for a client and policy (return to default behavior).
cacontrol --sth delete <STHTYPE> <CLIENT> <POLICY> [SPAUSER]
You can disable the stream handler on a client and policy.
cacontrol --sth update <STHTYPE> <CLIENT> <POLICY> [SPAUSER] <disabled>
You can query the settings for the stream handler per policy.
cacontrol --sth getbypolicy <STHTYPE> <POLICY> [SPAUSER]
You can enable the stream handler per policy.
cacontrol --sth updatebypolicy <STHTYPE> <POLICY> [SPAUSER] <enabled>
You can delete the settings for the stream handler per policy (return to default behavior).
cacontrol --sth deletebypolicy <STHTYPE> <POLICY> [SPAUSER]
You can disable the stream handler per policy.
cacontrol --sth updatebypolicy <STHTYPE> <POLICY> [SPAUSER] <disabled>
You can query the settings for the stream handler per stream handler type.
cacontrol --sth getbytype <STHTYPE> [SPAUSER]
You can enable a stream handler per stream handler type.
cacontrol --sth updatebytype <STHTYPE> [SPAUSER] <enabled>
You can delete the settings for a stream handler (return to default behavior).
cacontrol --sth deletebytype <STHTYPE> [SPAUSER]
You can disable the stream handler per stream handler type.
cacontrol --sth updatebytype <STHTYPE> [SPAUSER] <disabled>