PowerProtect: How To Migrate Protect Data Manager Components to a Different vCenter

It is highly recommended that you verify that there has been a recent successful Server Disaster Recovery (DR) backup. This is recommended when making any major changes, and is required for migrating the Search Engines. Complete these PowerProtect Data Manager component migrations before removing the old vCenter from PowerProtect Data Manager. 

• Protect Data Manager Server: Add the new vCenter as an Asset Source. Once the PowerProtect Data Manager has been migrated to the new vCenter, update the hosting vCenter.
• Search Engine: Deploy a fresh Search Engine on new vCenter. DR restores each Search Engine. Instructions for this can be found in the "Recover the Search Engine from a DR backup" section of the PowerProtect Data Manager Administrator Guide.
• VM Direct Engines: These are stateless data movers. They do not hold any backup data. They should be deleted from PowerProtect Data Manager and old vCenter, and redeployed fresh on the new vCenter.
• NAS Protection Engine: These are stateless data movers. They do not hold any backup data. They should be deleted from PowerProtect Data Manager and old vCenter, and redeployed fresh on the new vCenter.

The following sections of the PowerProtect Data Manager Virtual Machine User Guide may also be of value for similar situations:

• Deleting vCenter asset sources or moving ESXi to another vCenter server
• Delete VM Direct Engines or Search nodes when a vCenter server asset source is deleted
• Return VM Direct or Search nodes to an operational state when readding a vCenter server

Documentation is found on the Dell Support PowerProtect Data Manager Product Page.