Veritas NetBackup™ Deduplication Guide
- Introducing the NetBackup media server deduplication option
- 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
- Configuring deduplication to the cloud with NetBackup Cloud Catalyst
- Using NetBackup Cloud Catalyst to upload deduplicated data to the cloud
- Configuring a Cloud Catalyst storage server for deduplication to the cloud
- MSDP cloud support
- About MSDP cloud support
- 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
- Troubleshooting
- About unified logging
- About legacy logging
- Troubleshooting MSDP installation issues
- Troubleshooting MSDP configuration issues
- Troubleshooting MSDP operational issues
- Troubleshooting Cloud Catalyst issues
- Cloud Catalyst logs
- Problems encountered while using the Cloud Storage Server Configuration Wizard
- Disk pool problems
- Problems during cloud storage server configuration
- Cloud Catalyst troubleshooting tools
- Trouble shooting multi-domain issues
- Appendix A. Migrating to MSDP storage
About Image Sharing using MSDP cloud
Image Sharing lets you use an easy and visualized way to manage and provision images in cloud object storage and even the ability to convert backed up VMs as AWS instances in certain scenarios. Image sharing also supports MSDP cloud.
Before you begin, see the following topics:
Things to consider before you use Image sharing: See About image sharing in cloud using Cloud Catalyst.
Using Image sharing: See About image sharing in cloud using Cloud Catalyst.
Additional information about Image sharing: See About image sharing in cloud using Cloud Catalyst.
After installing NetBackup, you can run the ims_system_config.py script to configure Image sharing.
The path to access the command is: /usr/openv/pdde/pdag/scripts/
Use the following command:
ims_system_config.py -t PureDisk -k <key_id> -s <secret_key> -b <bucket_name> -bs <bucket_sub_name> [-r <bucket_region>] [-p <mount_point>]
Use the following command:
ims_system_config.py -cp 2 -t PureDisk -k <key_id> -s <secret_key> -b <container_name> -bs <bucket_sub_name> [-p <mount_point>]
Use the following command:
# ims_system_config.py -cp 3 -t PureDisk -k <key_id> -s <secret_key> -b <bucket_name> -bs <bucket_sub_name> -pt <cloud_provider_type> -sh <s3_hostname> -sp <s3_http_port> -sps <s3_https_port> -ssl <ssl_usage>
Note:
Do not use nbdevconfig to modify cloud LSU or add new cloud LSU in image sharing server, that might cause an issue in the image sharing server.
If Amazon Glacier or deep Archive is enabled in MSDP cloud, you cannot use Image sharing.
As there is a requirement of free disk spaces by cloud LSU, ensure that you have enough disk space in the default mount point /storage, or you can use -p parameter of ims_system_config.py to specify a different mount point to meet the requirement of free disk spaces.