Is there some kind of trick to renaming vsa pseudoclients?

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

@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.

@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.

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.