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
PutObject (snowball-auto-extract for small files)
Each copy operation has some overhead; therefore, performing many transfers on individual small files has slower overall performance than transferring the same data in larger files. To significantly improve your transfer speed for small files (files less than 1 MB), batch the small files together. Batching files is a manual process. If the batched files are put to S3 server with the x-amz-meta-snowball-auto-extract header, the batches are automatically extracted when data is imported MSDP S3 Server.
Note:
The x-amz-meta-snowball-auto-extract header is not accepted for un-versioned bucket, and all the batched small files share the same version in S3 server.
Run the tar or gzip command to manually batch small files, and then transfer them to S3 interface for MSDP.
For example: tar -czf <archive-file> <small files or directory of small files>
aws --endpoint https://<hostname>:8443 --profile <profile name> s3api [--ca-bundle <CA_BUNDLE_FILE>] put-object --bucket <bucket name> --key <key path> --body <xxx.tgz> --metadata snowball-auto-extract=true
Keep in mind the following when batching small files:
Maximum batch size of 5 GB.
Recommended maximum of 10,000 files per batch.
Supported archive formats are TGZ.
Request Syntax
PUT /bucket/Key HTTP/1.1 Host: msdps3.server:8443 Content-Length: ContentLength Content-MD5: ContentMD5 x-amz-meta-snowball-auto-extract:true Body
Request Parameters
Bucket
Name of the bucket.
Required: Yes
Type: String
Key
Name of the object.
Required: Yes
Type: String
x-amz-object-lock-mode (Flex WORM only)
The Object Lock mode that you want to apply to this object.
Valid Values: GOVERNANCE, COMPLIANCE
x-amz-object-lock-retain-until-date (Flex WORM only)
The date and time when you want this object's Object Lock to expire. Must be formatted as a timestamp parameter.
Request Headers
Enable snowball-auto-extract
Required: Yes
Value: true
Response Syntax
HTTP/1.1 200 ETag: ETag x-amz-version-id: VersionId
Request Headers
x-amz-version-id
The version-id of the object PUT in the bucket.
Possible Error Response
Success
HTTP status code 200.
EntityTooLarge
The object size exceeded maximum allowed size.
HTTP status code 400.
AccessDenied
Request was rejected because user authentication failed.
HTTP status code 403.
NoSuchBucket
The specified bucket does not exist.
HTTP status code 404.
InternalError
Request failed because of an internal server error.
HTTP status code 500.
InvalidRequest
The error may occur for some reasons. For details, please refer the error messages.
HTTP status code 400.