I am looking for any advice, tips, pitfalls to avoid, things we should consider and such, with regards to plans for getting from the current commvault installation, to a planned new commvault installation.
5+ year old (but updated) installation, with 1 virtual commcell, and 4 physical media-agents, 2 in each datacenter. Physical HW for both the media-agents and the storage are reaching their EOL in 2022 and needs replacing.
The Commvault environment is currently in the production domain.
New Installation (planned):
New installation, with 1 virtual commcell (or possibly clustered?) and 4 virtual media-agents, 2 in each datacenter.
The Commvault environment and the underlying virtualization servers for the Commvault CS/MA VMs should be in a completely separate domain from the production domain they are taking backups of.
New storage will be 25Gbps iSCSI (or NVMeoF or NVMe/TCP) based.
Now, the question is i guess, what would be the most sensible way to get from A to B.
I am tempted to start with a clean slate, and install a completely new Commvault environment, and then "move" backup clients, 1 at a time, by stopping/disabling the schedule/jobs in the old environment.
Then uninstalling the agent(s) & reinstalling the agents on a client and point it to the new solution, then make/define new jobs/Schedules for each client moved over. This will move the client to the new environment, but as i've understood it, we could still
do restores in the old environment, aslong as we restore to a different location/target.
Then move clients over one by one until all clients are controlled by the new installation.
Does this sound like a sensible plan, or are there other ways of doing this that would be better ?
Any advice, tips and such are welcome.