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
Changing the MSDP storage server name or storage path
Two aspects of a NetBackup deduplication configuration exist: the record of the deduplication storage in the EMM database and the physical presence of the storage on disk (the populated storage directory).
Warning:
Deleting valid backup images may cause data loss.
See About changing the MSDP storage server name or storage path.
Table: Changing the storage server name or storage path
Step | Task | Procedure |
---|---|---|
Step 1 |
Ensure that no deduplication activity occurs |
Deactivate all backup policies that use deduplication storage. See the NetBackup Administrator's Guide, Volume I: http://www.veritas.com/docs/DOC5332 http://www.veritas.com/docs/DOC5332 |
Step 2 |
Expire the backup images |
Expire all backup images that reside on the deduplication disk storage. Warning: Do not delete the images. They are imported back into NetBackup later in this process. If you use the bpexpdate command to expire the backup images, use the -nodelete parameter. See the NetBackup Administrator's Guide, Volume I: http://www.veritas.com/docs/DOC5332 http://www.veritas.com/docs/DOC5332 |
Step 3 |
Delete the storage units that use the disk pool |
See the NetBackup Administrator's Guide, Volume I: http://www.veritas.com/docs/DOC5332 http://www.veritas.com/docs/DOC5332 |
Step 4 |
Delete the disk pool | |
Step 5 |
Delete the deduplication storage server | |
Step 6 |
Delete the configuration |
Delete the deduplication configuration. |
Step 7 |
Delete the deduplication host configuration file |
Each load balancing server contains a deduplication host configuration file. If you use load balancing servers, delete the deduplication host configuration file from those servers. |
Step 8 |
Delete the identity file and the file system table file |
Delete the following files from the MSDP storage server, depending on operating system: UNIX: /storage_path/data/.identity /storage_path/etc/puredisk/fstab.cfg Windows: storage_path\data\.identity storage_path\etc\puredisk\fstab.cfg |
Step 9 |
Change the storage server name or the storage location |
See the computer or the storage vendor's documentation. |
Step 10 |
Reconfigure the storage server |
When you configure deduplication, select the host by the new name and enter the new storage path (if you changed the path). You can also use a new network interface. |
Step 11 |
Import the backup images |
See the NetBackup Administrator's Guide, Volume I: http://www.veritas.com/docs/DOC5332 http://www.veritas.com/docs/DOC5332 |