Migrate to a different
Microsoft Exchange Server host
You can migrate to a different
Microsoft Exchange Server host and connect it with
PowerProtect Data Manager by reusing the IP address and hostname of the former host.
Prerequisites
Delete the host by deleting the asset source according to
Delete an asset source. This procedure unregisters the host from
PowerProtect Data Manager and removes the host assets after all the asset copies have expired.
The assets and asset source of the original host are still in the "Deleted" state, unless the asset copies have expired and garbage collection has run.
NOTE:If you unregister and reregister the Microsoft application agent instead of completing this deletion step, then duplicated asset names might appear in the
PowerProtect Data Manager UI.
Ensure that the operating system of the former application host is powered off.
About this task
This procedure is applicable for the following use cases:
Host server is deleted, and the application agent is migrated to a new host that uses the same IP address and hostname as the former host.
The operating system version of the new application host can be the same or different from the operating system version of the former host.
Steps
Disable the protection policy.
NOTE:Only disable the protection policy if the affected
Microsoft Exchange Server host is the only host that this policy protects.
Register the new host with
PowerProtect Data Manager.
If you specify the same IP address and hostname as the former host,
PowerProtect Data Manager registers the new host using the same agent ID.
Restore the data from the former host on the new host.
Enable the protection policy to continue with the scheduled backups.
NOTE:If you did not disable the protection policy, any associated assets that are protected by the protection policy are removed automatically. Add the required assets back into the policy to continue protecting the assets.
Data is not available for the Topic
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\