On cloned server with same IP can not start backup Commvault

Hi Elizabeta,

Can you confirm whether the old server is still online in the environment?

Is it using a different IP address now?

Are the Commvault services started on that machine?

Is there a network topology in place that might be causing the older machine to be creating tunnels back to the Commserve?

I always recommend uninstalling Commvault from the server you are cloning prior to the clone operation and then re-installing on the freshly cloned server (depending on which agents are in use) since I have seen it cause problems in several cases.

Uninstalling the binaries will deconfigure the client in the Commcell and then re-installing on the new server should use the same client entity once installation is completed, keeping the backup history in-tact for the client.

If the old server is still online with Commvault installed, stop the services on both the old and new server and then restart just the new server and see if backup is able to complete. If there are still issues I would recommend uninstalling the Commvault binaries on both machines and re-installing them on the new machine again. 

Regards,

David Dwyer

Hello David,

Thank you for your answer.
The old server is shut down, the new cloned server is using the same IP address.
Commvault services are running on the new cloned machine.

Could you please tell me what the procedure is for uninstalling Commvault from the old server?
On the Commvault console there is an option Release License for Client. Should that be done and then Delete Client, or should we not delete the client (new cloned) but only use Release License for Client, uninstall Commvault, and then simply install the Commvault software again?

Best regards,
Elizabeta

Hi Elizabeta,

DO NOT DELETE THE CLIENT!!! Unless you are OK with losing the backup history of that machine.

I would simply uninstall the binaries on the new server via Windows appwiz and then use the bootstrap installer to run the install again. 

You can refer to the documentation for uninstallation here for the various methods: 

https://documentation.commvault.com/11.40/commcell-console/uninstall_commvault_from_client_and_mediaagent_computers.html

Uninstalling the binaries should release the license in the Commcell (in theory, but since there seem to be issues already, maybe not). 

When you re-install the binaries it should re-register with the same client entity that exists in the environment.

Installations: https://documentation.commvault.com/11.40/commcell-console/client_installations.html

So my recommended steps from this point:

1. Ensure that the old machine is definitely powered off or at least completely removed from the network so as to not be able to attempt communication with the Commserve (I only request this because the number of cases I’ve seen where the VM was still powered on despite assurances it wasn’t).
2. ​​​​​​​On the new machine, run appwiz.cpl and then use the application wizard to uninstall Commvault.
3. With the setup media, reinstall Commvault.
4. Verify that the client entity in the Commcell is now re-licensed and back online and able to check readiness.

For future such events, the procedure I’ve recommended many times is:

1. Uninstall Commvault prior to cloning the machine.
2. Clone the machine.
3. Reinstall Commvault on the new machine.

If you have any concerns or need assistance with any of the above I would recommend opening a support case to assist further.

I hope this helps.

Regards,
David Dwyer