Skip to main content
Question

Duplicate Clients for VM SQL and FS agent

  • 20 June 2024
  • 4 replies
  • 40 views

Hello all!

We do have a problem with a Windows server.

There was server XYZ which was migrated to Server 2022.

So a new server with the same name was created in VMware XYZ

The old server was stopped, and new server was addressed with the same IP.

Old server was renamed in VMware to XYZ_old.

And now we do have a problem….

We do have two entries in Commvault
XYZ and XYZ_old

For VMware snapshot XYZ is our server which will be backed up.
But after installation of SQL and FS Core package on NEW server it somehow appears on XYZ_old server… and whats even funnier i am able to browse server, and configure SQL backup.

 

So wo have two entities in commvault now:

XYZ_old which contains an FS and SQL agent

XYZ which contains VM backup.

 

In VMware the original XYZ server is not existing any more! it was deleted. I have released licensees for the old server, reconfigured it, retired and tried to change ip, but still when we install FS core on this server it continues to install on the XYZ_old…

We have tried to merge this, but commvault does not allow us to do so.

 

Is there a way to fix this?

 

4 replies

A
Rank
Userlevel 6
Badge +15

Hello  @Grzegorz 


Thanks for the update and details, it seems that some parts of the environment is seeing this as two machines when the other parts as a single. 
I recommend a support ticket to review this one and undo these issues. 

 

Kind regards

Albert Williams

The best way to learn anything, is to question everything
G
Rank
Badge +5

Hi! Many thanks for response!

We do have created a Commvault support case for that.

Lets hop it will be solved quick and easy!

A
Rank
Userlevel 6
Badge +15

Thanks for the update, if you do resolve it please update this thread so we know what caused it!

Kind regards

Albert Williams

The best way to learn anything, is to question everything
G
Rank
Badge +5

Hi!

For now, what we did was to run a script from CMD as a Administrator →

qlogin 

qoperation execscript -sn QS_MoveVMPropandJobs -si 'XYZ_old' -si 'XYZ'

 

It did not remove those duplicated entries, the old one is still present, but VM backup has moved to desired one and XYZ_old is used as an entry to keep old VM backup, which also seems a good solution since it was actually the other server.

Now we are working to re-enable SQL backup on the server, but what we have done might be useful for other in similar case.

Many thanks for all your tips!

Reply


Terms & ConditionsCookie settings