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
ListMultipartUploads
Lists in-progress multipart uploads. An in-progress multipart upload is a multipart upload that is initiated using the Create Multipart Upload request but is not complete yet or aborted. This operation randomly returns a maximum of 10000 multipart uploads in the response that is sorted by object key in ascending order. The operation does not support paging.
Request Syntax
GET /bucket?uploads&prefix=Prefix Host: msdps3.server:8443
Request Parameters
Bucket
Name of the bucket on which the multipart upload was initiated.
Required: Yes
Type: String
prefix
Limits the response to uploads that begin with the specified prefix.
Type: String
Response Syntax
HTTP/1.1 200 <?xml version="1.0" encoding="UTF-8"?> <ListMultipartUploadsResult> <Bucket>string</Bucket> <KeyMarker>string</KeyMarker> <UploadIdMarker>string</UploadIdMarker> <NextKeyMarker>string</NextKeyMarker> <Prefix>string</Prefix> <NextUploadIdMarker>string</NextUploadIdMarker> <MaxUploads>integer</MaxUploads> <IsTruncated>boolean</IsTruncated> <Upload> <Initiated>timestamp</Initiated> <Key>string</Key> <StorageClass>string</StorageClass> <UploadId>string</UploadId> </Upload> ... </ListMultipartUploadsResult>
Response Body
ListMultipartUploadsResult
Root level tag for the ListMultipartUploadsResult parameters.
Required: Yes
Bucket
Name of the bucket on which the multipart upload was initiated.
IsTruncated
A flag indicating whether all the results satisfying the search criteria were returned by MSDP S3.
KeyMarker
S3 interface for MSDP expects the key-marker which was returned by server in last request. The value of "NextKeyMarker" of response should be used in request as key-marker.
MaxUploads
Limits the number of multipart uploads that are returned in the response.
NextKeyMarke
When the response is truncated, you can use this value as marker in subsequent request to get next set of objects.
NextUploadIdMarker
When the response is truncated, you can use this value as marker in subsequent request to get next set of objects.
UploadIdMarker
The value of UploadIdMarker passed in the request.
Prefix
Limits the response to keys that begin with the specified prefix.
Upload
Information that is related to a particular multipart upload. Response can contain zero or multiple uploads.
Initiated
The time and date when the multipart upload was initiated.
Type: Timestamp
Key
Object name for which multipart upload was initiated.
StorageClass
Storage class of the uploaded part.
UploadId
Upload ID that identifies the multipart upload.
Possible Error Response
Success
HTTP status code 200.
InvalidArgument
Invalid Argument. 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.