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
- 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 immutable object support for AWS S3 compatible platforms
- About immutable storage support for Azure blob storage
- About immutable storage support for Google Cloud Storage
- 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
- Monitoring deduplication activity
- 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
- Using the ingest mode
- Enabling a universal share with object store
- Configuring isolated recovery environment (IRE)
- Using the NetBackup Deduplication Shell
- Managing users from the deduplication shell
- 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 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
Configuring S3 interface for MSDP on MSDP build-your-own (BYO) server
After MSDP is configured, you can run s3srv_config.sh
to configure S3 interface for MSDP.
To configure S3 server
- If you want to use NBCA or ECA type certificates in S3 interface for MSDP, run the following command:
/usr/openv/pdde/vxs3/cfg/script/s3srv_config.sh --catype=<type> [--port=<port>] [--loglevel=<0-4>]
If you want to use your certificates in S3 interface for MSDP, run the following command:
/usr/openv/pdde/vxs3/cfg/script/s3srv_config.sh --cert=<certfile> --key=<keypath> [--port=<port>] [--loglevel=<0-4>]
--catype=<type> | Certificate Authority type. NBCA: 1 or ECA: 2. |
--cert=<certfile> | Certificate file for HTTPS. |
--key=<keypath> | Private key for HTTPS. |
--port=<port> | S3 server port. Default port is 8443. |
--loglevel=<0-4> | S3 server log level.
|
--help|-h | Print the usage. |
S3 service is HTTPS service. Default port is 8443.
If multiple certificates exist under
/usr/openv/var/vxss/credentials
, you may see the following configuration error:Too many ca files under /usr/openv/var/vxss/credentials/keystore
You can use option --cert and --key to specify which certificate is used.
You can enable HTTPS with the certificate, which is not signed by Certificate Authority in S3 interface for MSDP. If S3 interface for MSDP is configured with NBCA as SSL certificate, CA certificate is
/usr/openv/var/webtruststore/cacert.pem
under S3 server host. When you use AWS CLI to connect S3 interface for MSDP, there are two options --ca-bundle and --no-verify-ssl. Option --ca-bundle verifies SSL certificates with corresponding CA certificate bundle. Option --no-verify-ssl overrides verifying SSL certificates in AWS CLI command. You can ignore the following warning message.urllib3/connectionpool.py:1043: InsecureRequestWarning: Unverified HTTPS request is being made to host 'xxxx.xxxx.com'. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/1.26.x/advanced-usage.html#ssl-warnings
Only PEM format of certificate and secret key is supported. Please convert other format of certificate and secret key to PEM format.
After configuring S3 server, you can check S3 server status.
systemctl status pdde-s3srv
After configuring S3 server, you can stop or start S3 server.
systemctl stop/start pdde-s3srv
NGINX configurations about S3 server are saved at
/etc/<nginx path>/conf.d/s3srvbyo.conf
and/etc/<nginx path>/locations/s3srv.conf
. If you have modified the configuration files, you must modify them again after the upgrade.