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
- 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
- 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 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
Replacing the MSDP storage server host computer
If you replace the deduplication storage server host computer, use these instructions to install NetBackup and reconfigure the deduplication storage server. The new host cannot host a deduplication storage server already.
Reasons to replace the computer include a lease swap or perhaps the current deduplication storage server computer does not meet your performance requirements.
NetBackup recommends that you consider the following items before you recover:
The new computer must use the same byte order as the old computer.
Warning:
If the new computer does not use the same byte order as the old computer, you cannot access the deduplicated data. In computing, endianness describes the byte order that represents data: Big endian and little endian. For example, SPARC processors and Intel processors use different byte orders. Therefore, you cannot replace an Oracle Solaris SPARC host with an Oracle Solaris host that has an Intel processor.
Veritas recommends that the new computer use the same operating system as the old computer.
Veritas recommends that the new computer use the same version of NetBackup as the old computer.
If you use a newer version of NetBackup on the new computer, ensure that you perform any data conversions that may be required for the newer release.
If you want to use an older version of NetBackup on the replacement host, contact your Veritas support representative.
Table: Replacing an MSDP storage server host computer
Step | Task | Procedure |
---|---|---|
Step 1 | 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: |
Step 2 | Delete the storage units that use the disk pool | See the NetBackup Administrator's Guide, Volume I: |
Step 3 | Delete the disk pool | |
Step 4 | Delete the deduplication storage server | |
Step 5 | 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 6 | Delete the credentials on deduplication servers | If you have load balancing servers, delete the NetBackup Deduplication Engine credentials on those media servers. |
Step 7 | Configure the new host so it meets deduplication requirements | When you configure the new host, consider the following:
|
Step 8 | Connect the storage to the host | Use the storage path that you configured for this replacement host. See the computer or the storage vendor's documentation. |
Step 9 | Install the NetBackup media server software on the new host | See the NetBackup Installation Guide for UNIX and Windows: |
Step 10 | Reconfigure deduplication | |
Step 11 | Import the backup images | See the NetBackup Administrator's Guide, Volume I: |
More Information