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
- 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
- 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
- Configuring deduplication to the cloud with NetBackup CloudCatalyst
- Using NetBackup CloudCatalyst to upload deduplicated data to the cloud
- Configuring a CloudCatalyst storage server for deduplication to the cloud
- 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
- About unified logging
- About legacy logging
- Troubleshooting MSDP installation issues
- Troubleshooting MSDP configuration issues
- Troubleshooting MSDP operational issues
- Troubleshooting CloudCatalyst issues
- CloudCatalyst logs
- Problems encountered while using the Cloud Storage Server Configuration Wizard
- Disk pool problems
- Problems during cloud storage server configuration
- CloudCatalyst troubleshooting tools
- Appendix A. Migrating to MSDP storage
Removing a trusted master server
To remove a trusted master server, you must perform the following procedure on both the source and the target server.
If either your source or the target server is on version 8.0 or earlier, follow the procedure that is prescribed in the respective guide.
To remove a trusted master server
- Ensure that all replication jobs to the trusted target master server are complete. You can use nbstlutil stlilist to list the state of all storage lifecycle policy-managed operations. To cancel jobs use nbstlutil cancel.
See the NetBackup Commands Reference Guide for information about the nbstlutil command.
- Delete all storage lifecycle policies (SLPs) that use the trusted master as a destination.
Before deleting a storage lifecycle policy, ensure that there are no backup policies that indicate the SLP for the Policy storage.
- In the NetBackup Administration Console, expand NetBackup Management > Host Properties > Master Servers in the left pane.
- In the right pane, select the master server.
- On the Actions menu, click Properties.
- In the properties dialog box left pane, select Servers.
- In the Servers dialog box, select the Trusted Master Servers tab.
- On the Trusted Master Servers tab, select the trusted master server that you want to remove and click Remove.
The Remove Server confirmation dialog box is displayed.
- Click Yes.
- When you finish removing trusted master servers, click OK.
- Restart the nbsl service.
- Repeat the steps on the source master server.
In case of multiple NICs, if you have established trust using more that one host NIC and if you remove the trust relationship with any one host NIC, the trust with all the other host NICs is broken.