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 Key Management Server 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
- Running MSDP services with the non-root user
- MSDP cloud support
- About MSDP cloud support
- Cloud space reclamation
- About the disaster recovery for cloud LSU
- About Image Sharing using MSDP cloud
- About MSDP cloud immutable (WORM) storage support
- About immutable object support for AWS S3
- About bucket-level immutable storage support for Google Cloud Storage
- About object-level immutable storage support for Google Cloud Storage
- About AWS IAM Role Anywhere support
- About Azure service principal support
- About NetBackup support for AWS Snowball Edge
- S3 Interface for MSDP
- Configuring S3 interface for MSDP on MSDP build-your-own (BYO) server
- Identity and Access Management (IAM) for S3 interface for MSDP
- S3 APIs for S3 interface for MSDP
- Disaster recovery in S3 interface for MSDP
- 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
- Configuring universal share user authentication
- Using the ingest mode
- Enabling a universal share with object store
- Configure a universal share accelerator
- About the universal share accelerator quota
- Configuring isolated recovery environment (IRE)
- Configuring an isolated recovery environment using the web UI
- Configuring an isolated recovery environment using the command line
- Using the NetBackup Deduplication Shell
- Managing users from the deduplication shell
- About the external MSDP catalog backup
- Managing certificates from the deduplication shell
- Managing NetBackup services from the deduplication shell
- Monitoring and troubleshooting NetBackup services from the deduplication shell
- Managing S3 service from the deduplication shell
- Troubleshooting
- About unified logging
- About legacy logging
- 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
Microsoft SQL Server stream handler
Microsoft SQL stream handler improves Microsoft SQL backup deduplication rate. You can apply the Microsoft SQL Server stream handler to all the Microsoft SQL Server versions and Azure SQL Server.
You can protect the Microsoft SQL database with NetBackup using the following methods:
MS-SQL-Server policy
Use MS-SQL-Server policy type to protect Microsoft SQL database. This policy type is the recommended way to protect the Microsoft SQL database.
In this case, the Microsoft SQL stream handler is enabled automatically. The policy has multiple options including a use of a user-provided batch file and intelligent policy.
Standard policy
Use a standard policy to protect Microsoft SQL dump files.
In this case, the user dumps Microsoft SQL Server to a file and creates a standard policy to back up the dumped file.
You must use cacontrol command to enable the Microsoft SQL stream handler manually.
Following are the cacontrol options that you can use to manage Microsoft SQL Server stream handler:
Table: The cacontrol command options
Option | Description |
---|---|
cacontrol --sth get <Oracle|MSSQL> <client> <policy> | Get the specified marker entry status. |
cacontrol --sth delete <Oracle|MSSQL> <client> <policy> | Delete the specified marker entry. |
cacontrol --sth update <Oracle|MSSQL> <client> <policy> <enabled|disabled> | Update the specified marker entry status. |
cacontrol --sth getbypolicy <Oracle|MSSQL> <policy> | Get the specified marker entry status for a given policy. |
cacontrol --sth deletebypolicy <Oracle|MSSQL> <policy> | Delete the specified marker entry for a given policy. |
cacontrol --sth updatebypolicy <Oracle|MSSQL> <policy> enabled|disabled | Update the specified marker entry status for a given policy. |
To use the Microsoft SQL Server stream handler
- Enable or disable the stream handler for a policy.
cacontrol --sth updatebypolicy MSSQL <POLICY name> enabled/disabled
- Delete the stream handler settings for a policy (returns to the default behavior). Microsoft SQL stream handler is enabled by default.
cacontrol --sth deletebypolicy MSSQL <POLICY name>
- Query the settings for the stream handler for a policy.
cacontrol --sth getbypolicy MSSQL <POLICY name>
- Enable or disable the stream handler for a policy and a client.
cacontrol --sth update MSSQL <Client name> <POLICY name> enabled/disabled
- Delete the stream handler settings for a policy and a client (returns to the default behavior). Microsoft SQL stream handler is enabled by default.
cacontrol --sth delete MSSQL <Client name> <POLICY name>
- Query the settings for the stream handler for a policy and a client.
cacontrol --sth get MSSQL <Client name><POLICY name>
- Verify that the Microsoft SQL stream handler is enabled or disabled.
On the NetBackup web UI, under the Job Details tab, MSSQL Stream Handler enabled is displayed.
When Client Direct setting is enabled, the Microsoft SQL stream handler is not used even if the MS-SQL-Server policy type is used. The pdplugin does not know the policy type when it runs on the client side.
To enable the stream handler, use the cacontrol command to enable the Microsoft SQL stream handler for the policy or the client and policy.
Do not enable the NetBackup compression settings when the storage type is MSDP. This setting causes deduplication loss even if the Microsoft SQL stream handler is enabled or disabled.
The Microsoft SQL compression setting is provided by Microsoft SQL Server. It compresses the SQL data. When Microsoft SQL native compression is enabled, the deduplication rate may drop.
Microsoft SQL stream handler works well with the Microsoft SQL Server Transparent Data Encryption (TDE). Microsoft SQL TDE only encrypts the SQL data and the SQL page structure does not change. The deduplication is not lost when the Microsoft SQL Server TDE is enabled.