Skip to main content
commvault.com commvault.com

Imagine the following situation:

 

  • You have a VM, with windows .
  • Machine is called VM1.
  • That VM1 has a file agent, and -for example- an Oracle system configured.
  • That VM1 is being cloned, on virtualization level, to VM2.
  • Of course, VM2 is being renamed on machine level to VM2. (hostname).

How can we reuse the same commvault agent VM1 settings, and “clone” it to VM2.

With that I mean : without reinstalling everything of commvault on VM2, and without the need to figure out the passwords which were used in VM1 Oracle agent.

You would need to reinstall the agent on the newly cloned machine. If the cloned machine is replacing the original, you can ‘edit’ the display\client\host names to match the new vm2 and all the settings\backups history would be saved. 

 

If you are running VSA backups, the cloned machine would have a new UUID so it would create a new machine in the GUI to represent it. 

Who marked this as the best answer? That's   not the case. 

You could install the agent in decoupled mode that would give you a vanilla agent, you just run either register me or us the new client option to connect to it.

Planning for the Custom Package Creation on Windows Computers (commvault.com)

Registering the Client Using the CommCell Console (commvault.com)

Or use this feature to autodetect the application instances when you install the FS agent.

Install Database Agents on Client Computers by Automatically Discovering Applications in the CommCell Console (commvault.com)

There are a few ways to do this. Is your goal a VM you can clone with all the agents preconfigured?

 

Reply


Terms & ConditionsCookie settings