Skip to main content
commvault.com commvault.com

Hello Commvault Community,

We have a scenario where we would like to separate an existing client in our Commvault environment into two distinct entities. Here's our situation:

  1. We have a SQL server that was originally on-premises and backed up entirely by Commvault.
  2. We've since migrated this server to Azure, but we're maintaining a hybrid backup approach:
    • Azure Backup is now handling most of the server's data
    • Commvault will be managing the SQL backups

We'd like to separate this into two distinct clients in Commvault:

  1. An on-premises client (historical/inactive) for our legacy data and backups, renamed with the onprem location as a suffix.
  2. A  new client for our current SQL backups with the same name without the suffix.

Our question is:

  • Is it possible to change the current client and its client identifier, so we can add the migrated client as new.
    It would be like a new installation using the same client name.

Any guidance on best practices for managing this kind of hybrid scenario and client separation would be greatly appreciated. Thank you in advance for your help!

 

BR
Henke

Hi Henke,

This sounds like installation of a new client after taking the local uninstallation of the old client and releasing its licence in the commcell.

I would not be too attached to the client identifier of the old client as such unless there is a business need to keep the clarity and consistency in the naming convention.

You may follow the below steps:

  • locally uninstall the old client and release its license in commcell
  • change the hostname and the displayname according to needs (add suffixes)
  • locally install Filesystem Core using client name and hostname of choice. Here, if the above is not done, you may be prompted if you want to keep the client under old install or create a new one. Create a new one then.
  • Then push the SQL agent form the commcell.

As a result, you should have two clients… one active and one deconfigured keeping the old backups.

Hi @Jacek Piechucki 

We did try the way you described, but that resulted in that the new install was merged into the old client, so it didn’t quite work the way we was hoping.

Instead we will go with nabling the setting so we can manually change the client identifier. 

Thanks

Henke

 

 

Reply


Terms & ConditionsCookie settings