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
CompleteMultipartUpload
Completes a multipart upload by assembling previously uploaded parts.
Request Syntax
POST /bucket/Key+?uploadId=UploadId HTTP/1.1 Host: msdps3.server:8443 <?xml version="1.0" encoding="UTF-8"?> <CompleteMultipartUpload xmlns="http://s3.amazonaws.com/doc/2006-03-01/"> <Part> <ETag>string</ETag> <PartNumber>integer</PartNumber> </Part> ... </CompleteMultipartUpload>
Request Parameters
Bucket
Name of the bucket.
Required: Yes
Type: String
Key
The name of the object.
Required: Yes
Type: String
uploadId
Upload ID of multipart upload.
Required: Yes
Type: String
Request body
CompleteMultipartUpload
Root level tag for the CompleteMultipartUpload parameters.
Required: Yes
Part
List of parts to create final object. It contains ETag and PartNumber.
ETag
ETag of the uploaded part.
PartNumber
PartNumber of the uploaded part.
Response Syntax
HTTP/1.1 200 x-amz-version-id: VersionId <?xml version="1.0" encoding="UTF-8"?> <CompleteMultipartUploadResult> <Bucket>string</Bucket> <Key>string</Key> <ETag>string</ETag> </CompleteMultipartUploadResult>
Response Headers
x-amz-version-id
Version ID of the created object.
Response Body
CompleteMultipartUploadResult
Root level tag for the CompleteMultipartUploadResult parameters.
Required: Yes
Bucket
Name of the bucket.
Required: Yes
Type: String
Key
The name of the object.
Required: Yes
Type: String
ETag
SHA256 digest of the object.
Possible Error Response
Success
HTTP status code 200.
InvalidDigest
The Content-MD5 you specified did not match what was received.
HTTP status code 400.
InvalidArgument
Invalid Argument.
Part number must be an integer between 1 and 10000, inclusive.
HTTP status code 400.
InvalidPartOrder
The list of parts was not in ascending order.
The parts list must be specified in order of the part number.
HTTP status code 400.
EntityTooLarge
Your proposed upload exceeds the maximum allowed object size.
HTTP status code 400.
ErrEntityTooSmall
Your proposed upload is smaller than the minimum allowed object size.
HTTP status code 400.
ErrNoSuchUpload
The specified multipart upload does not exist. The upload ID might not be valid, or the multipart upload might have been aborted or completed.
HTTP status code 400.
ErrInvalidPart
One or more of the specified parts could not be found. The part may not have been uploaded, or the specified entity tag may not match the part's entity tag.
HTTP status code 400.
MalformedPOSTRequest
The body of your POST request is not well-formed multipart/form-data.
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.