commvault.com commvault.com
Solved

Is there some kind of trick to renaming vsa pseudoclients?

  • 18 September 2023
  • 6 replies
  • 97 views
christopherlecky
Rank
Userlevel 5
Badge +16

I have a number of VSA psuedoclients that need to renamed but the option simply isn't there.

Am I missing something simple?

 

I can’t imagine this is a real issue.

icon

Best answer by Rajiv 19 September 2023, 08:35

View original
I blame auto-correct for all misspellings, grammatical errors, and half-baked opinions.

6 replies

Rajiv
Rank
Userlevel 4
Badge +11

Hello @christopherlecky 

Please add the Additional Setting on the Commserve properties:

====================================================

Name: bAllowModifyClientName

Category: CommServDB.Console

Type: BOOLEAN

Value: True

=====================================================

This has been done as a part of security and please make sure to remove the setting once the renaming of the pseudo client is done. 

Best,

Rajiv Singal

S
Rank
Userlevel 6
Badge +14

Hi @christopherlecky ,

The ability was restricted for a reason, so if possible I’d use this as last resort and only if really needed.

Best Regards,

Sebastien

christopherlecky
Rank
Userlevel 5
Badge +16

@Rajiv Thank you.

 

@Sebastien Merluzzi , thats pretty ominous.

can you elaborate? The goal is essentially cleanup. If it poses significant risk I wont do it.

I blame auto-correct for all misspellings, grammatical errors, and half-baked opinions.
S
Rank
Userlevel 6
Badge +14

@christopherlecky ,

You can check here: 

 

christopherlecky
Rank
Userlevel 5
Badge +16

@christopherlecky ,

You can check here: 

 

I checked and @Orazan  said

The Client name is an internal unique identifier for Commvault client entities.  The ability to remove it was made as Development does not want this changed as it would possibly interfere in our network identity communication in the future

 

But what does that mean? These are vm pseudo clients where the name don’t get honored anyway.

The current names are unresolvable and the backups work because vm pseudo clients seems to only pay attention to the instance properties.

I’m not trying to be difficult but this doesn't really tell me if the risk applies to what I want to do.

I blame auto-correct for all misspellings, grammatical errors, and half-baked opinions.
christopherlecky
Rank
Userlevel 5
Badge +16

So I went through with it.

The immediate effect was that client discovery was failing.

Checked the logs, It’s failing to rename the vm group because it already exists.

Deleted the VM group manually discovery runs, backup runs.

 

Sincerely thanks to @Sebastien Merluzzi @Rajiv 

I appreciate the help and the warning. 

Both helped.

I blame auto-correct for all misspellings, grammatical errors, and half-baked opinions.

Reply


Terms & ConditionsCookie settings