MediaAgent Hardware Refresh - FAQ
- What do I do if the MediaAgent is used for Disaster Recovery Backups?
- What do I do if the MediaAgent is hosting the deduplication database?
- Do I have to rebuild my local index cache in the new MediaAgent?
- What do I do if I have other types of tape library configurations?
- Will my Auxiliary Copy get affected if I decommission my old MediaAgent?
If the old MediaAgent is used for Disaster Recovery backups, then after successful migration of libraries, you must make the new MediaAgent as the default data path for the Disaster Recovery Storage Policy.
- From the CommCell Browser, navigate to Policies | Storage Policies.
- Right-click the CommServeDR storage policy, and then click Properties.
- Click the Data Paths.
- Click Add.
- In the Copy Data Path Candidates dialog box, select the new MediaAgent, and then click OK.
- Select the new MediaAgent and then click Set Default.
- Click OK.
If the old MediaAgent is hosting the deduplication database (DDB), you must move the ddb to a new MediaAgent. For instructions, see Moving the DDB to the New MediaAgent.
By default, the index cache is located in the MediaAgent installation folder. For the local index cache path, you do not need to copy the content of the index cache because the new MediaAgent can perform index restores from the media once the data is migrated.
Disconnect the tape library from the old MediaAgent, and then connect the tape library to the new MediaAgent. Do not deconfigure the library from the CommCell Console.
Once you attach the tape library, detect the device and re-configure the library. See Migrating the Libraries to new MediaAgent for more information.
Auxiliary Copy operation will not get affected when you migrate a MediaAgent to a new hardware as long as the data path is properly established as described in Setting the New MediaAgent as a Data Path section.