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
- About the MSDP Deduplication Multi-Threaded Agent
- About MSDP fingerprinting
- Enabling 400 TB support for MSDP
- About MSDP Encryption using NetBackup Key Management Server service
- Configuring a storage server for a Media Server Deduplication Pool
- About disk pools for NetBackup deduplication
- Configuring a Media Server Deduplication Pool storage unit
- Configuring client attributes for MSDP client-side deduplication
- About MSDP encryption
- About a separate network path for MSDP duplication and replication
- About MSDP optimized duplication within the same domain
- Configuring MSDP replication to a different NetBackup domain
- About NetBackup Auto Image Replication
- Configuring a target for MSDP replication to a remote domain
- About storage lifecycle policies
- Resilient network properties
- About variable-length deduplication on NetBackup clients
- About the MSDP pd.conf configuration file
- About saving the MSDP storage server configuration
- About protecting the MSDP catalog
- About NetBackup WORM storage support for immutable and indelible data
- Running MSDP services with the non-root user
- MSDP volume group (MVG)
- About the MSDP volume group
- Configuring the MSDP volume group
- 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
- About the cloud direct
- 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 managing universal shares
- Introduction to universal shares
- Prerequisites to configure universal shares
- Managing universal shares
- Restoring data using universal shares
- Advanced features of universal shares
- Direct universal share data to object store
- Universal share accelerator for data deduplication
- Configure a universal share accelerator
- About the universal share accelerator quota
- Load backup data to a universal share with the ingest mode
- Managing universal share services
- Troubleshooting issues related to universal shares
- 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
Editing an MSDP storage server configuration file
To use a storage server configuration file for recovery, it must contain only the required information. You must remove any point - in - time status information. (Status information is only in a configuration file that was saved on an active storage server.) You also must add several configuration settings that are not included in a saved configuration file or a template configuration file.
Table: Required lines for a recovery file shows the configuration lines that are required.
Table: Required lines for a recovery file
Configuration setting | Description |
---|---|
V7.0 "storagepath" " " string |
The value should be the same as the value that was used when you configured the storage server. |
V7.0 "spalogpath" " " string |
For the spalogpath, use the storagepath value and append log to the path. For example, if the storagepath is |
V7.0 "dbpath" " " string |
If the database path is the same as the storagepath value, enter the same value for dbpath. Otherwise, enter the path to the database. |
V7.0 "required_interface" " " string |
A value for required_interface is required only if you configured one initially; if a specific interface is not required, leave it blank. In a saved configuration file, the required interface defaults to the computer's hostname. |
V7.0 "spalogretention" "7" int |
Do not change this value. |
V7.0 "verboselevel" "3" int |
Do not change this value. |
V7.0 "replication_target(s)" "none" string |
A value for replication_target(s) is required only if you configured optimized duplication. Otherwise, do not edit this line. |
V7.0 "spalogin" "username" string |
Replace username with the NetBackup Deduplication Engine user ID. |
V7.0 "spapasswd" "password" string |
Replace password with the password for the NetBackup Deduplication Engine user ID. |
V7.0 "encryption" " " int |
The value should be the same as the value that was used when you configured the storage server. |
V7.0 "kmsenabled" " " int |
The value is used to enable or disable MSDP KMS configuration. The value should be the same as the value that was used when you configured the storage server. |
V7.0 "kmsservertype" " " int |
The value is KMS server type. This value should be 0. |
V7.0 "kmsservername" " " string |
The value is NBU Key Management Server. The value should be the same as the value that was used when you configured the storage server. If you use an external KMS as a KMS server, the value must be the NetBackup primary server name. See External KMS support in NetBackup in the NetBackup Security and Encryption Guide. |
V7.0 "keygroupname" " " string |
The value should be the same as the value that was used when you configured the storage server. |
To edit the storage server configuration
- If you did not save a storage server configuration file, get a storage server configuration file.
- Use a text editor to enter, change, or remove values.
Remove lines from and add lines to your file until only the required lines (see Table: Required lines for a recovery file) are in the configuration file. Enter or change the values between the second set of quotation marks in each line. A template configuration file has a space character (" ") between the second set of quotation marks.