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
Managing the Veritas provisioning file system (VPFS) configuration parameters
The Veritas provisioning file system (VPFS) is a service for Instant Access and Universal Shares. The default VPFS configuration works for most environments. However, you can adjust the parameters if needed. Some of the parameters that may affect performance include:
numOfInstance
This parameter specifies the number of vpfsd instances. A universal share uses one vpfsd instance by default. In most cases, one instance is adequate. Increasing the number of vpfsd instances might improve universal share performance, although it also requires more CPU and memory. You can increase the number of vpfsd instances from 1 to up to 16 and distribute the shares cross all the
vpfsd
instances.CloudCacheSize
This parameter specifies the local disk cache size. This option applies only to Universal Shares with object store and Instant Access with object store.
Use the following procedures to manage the VPFS configuration parameters.
To view a VPFS configuration parameter
- Open an SSH session to the server.
- Run the following command:
setting vpfs-config get-vpfs-param vpfs_configkey=<parameter>
Where <parameter> is the parameter that you want to view.
To change a VPFS configuration parameter
- Open an SSH session to the server.
- Run the following command:
setting vpfs-config set-vpfs-param vpfs_configkey=<parameter> vpfs_configvalue=<value>
Where <parameter> is the parameter that you want to change, and <value> is the value that you want to change it to. For example:
setting vpfs-config set-vpfs-param vpfs_configkey=numOfInstance vpfs_configvalue=2
To temporarily change the log level of a VPFS share
- Open an SSH session to the server.
- Run the following command:
setting vpfs-config set-log-level vpfs_loglevel=<level> vpfs_shareid=<share ID>
Where <level> is debug, information, or error, and <share ID> is the ID of the share that you want to change the log level of. For example:
setting vpfs-config set-log-level vpfs_loglevel=debug vpfs_shareid=my-db-share
Note:
This command is meant for a short debugging session, and the change is not preserved if you restart the instance. To permanently change the log level, use the following command:
setting vpfs-config set-vpfs-param vpfs_configkey=logLevel vpfs_configvalue=<level>
The default log level is information.