What is the best migration strategy?
1- Prepare a new machine, with a new IP and new hostname, install and configure everything (it is possible that there will be a problem with licensing, because I don't know if we can have two CommServe instances running at the same time) and after everything is ready, point the clients for that new host?
Or
2- Create a new machine, install and configure all related CommVault services, and on migration day, change that new machine's name and IP to reflect the environment's current CommServe hostname and IP?
Obs.: I remember that I would not like to bring jobs, policies, any configuration of the current CommServe, I would like to configure and review everything from scratch, in order to review the entire current environment and eliminate possible gaps.
I understand that for my case, option number 1 would be the most ideal, but I don't know the complexity of making all the clients that today point to CommServe A (for example) point to CommServe B, on the migration day.
And I also have questions about how to configure jobs, clients, storage and scheduling policies with the current CommServe running (can you configure clients to point to two CommServe at the same time?).
What is the best migration strategy that causes as little disruption to the backup service as possible?