commvault.com commvault.com
Solved

client installation in decoupled mode

  • 29 March 2021
  • 3 replies
  • 2364 views
B
Rank
Userlevel 4
Badge +14

Hello,

I am trying to make an install in decoupled mode on a linux machine,

 

I have created the custom package and installed the RPM.


then I ve used this command to register the client on commserve:

 

sudo /opt/commvault/Base/SIMCallWrapper -OpType 1000 -CSHost commserve.customer.com -clientname <vmclientname> -ClientHostName <vmClientHostName.customer.com> -authcode 123DGFJEJ -output /tmp/insatlcv.xml -restartServices

When I compare a manuel vs decoupled installation,  here is what I have :

 

Manual Install

[ General ]
 Version = 11.22.13
 Media Revision = 871
 CommServe Host Name = cs01.customer.com
 CommServe Client Name = commserve
 Home Directory = /opt/commvault/Base
 

from a machine installed in decouple mode 

[ General ]
 Version = 11.22.13
 Media Revision = 871
 CommServe Host Name = commserve.customer.com
 CommServe Client Name = commserve

The client is registered correctly in the commserve but some things are different

 

do you know why I don’t have the same informations from the manual and decoupled install. maybe my command is not correct ? 

commserve is the alias for dr failover. cs01.customer.com is the Commserve hostname.

Thanks !

icon

Best answer by MichaelCapon 30 March 2021, 10:33

View original

3 replies

S
Rank
Userlevel 7
Badge +15

Hi @Bloopa 

Thank for the question, it looks like your de-coupled installation command is specifying the name as commserve.customer.com:
 

sudo /opt/commvault/Base/SIMCallWrapper -OpType 1000 -CSHost commserve.customer.com -clientname <vmclientname> -ClientHostName <vmClientHostName.customer.com> -authcode 123DGFJEJ -output /tmp/insatlcv.xml -restartServices

If this name is resolvable to an active Commserve, then this will be used and recorded on the client.

When performing a manual, online installation, the Commserve will provide it’s hostname as it is configured on the Commserve client, so that might be where the difference is.

Please check the Commserve client name and check the details are as expected.

If there is a difference, there are options for updating Commserve hostname on clients if they have been configured with an incorrect (but operational) name.

Thanks,

Stuart

 

Customer Support
B
Rank
Userlevel 4
Badge +14

 

 

Hi @Stuart Painter 

Thanks for your answer

 

if I right clic on Commserve

commCell Name : commserve
CommCell Host Name : cs01.customer.com


on all my Windows machines installed manually :

process manager on the local machine
Commserve Hostname : cs01.customer.com
Commserve Name : commserve

 

same machine but right clic on VM properties :

Name : vmname

Displayname : vmname

Commserve hostname : cs01.customer.com

 

all machines installed with decoupled mode

example on linux machines :

 

right clic on VM properties :

Name : vmname

Displayname : vmname

hostname : vmname.customer.com

Commserve HostName : commserve.customer.com

 

commvault status on the local machine
Commserve Hostname : commserve.customer.com
Commserve Name : commserve

 

Check readyness is ok on all VMs

Just to be sure also, is it normal that the commserve HostName and ClientName appears with @@COMMSERVE@@ ?

 

[root@vmname CV_CustomPackages]# commvault -all status

--------------------------------- Instance001 ---------------------------------

[ General ]

 Version = 11.22.13

 Media Revision = 871

 CommServe Host Name = @@COMMSERVE@@

 CommServe Client Name = @@COMMSERVE@@

 

 

MichaelCapon
Rank
Userlevel 6
Badge +14

Hi Bloopa,


For the affected Machine, Can you confirm the values set for sCSCLIENTNAME and sCSHOSTNAME in the following files:

/etc/CommVaultRegistry/Galaxy/Instance001/iDataAgent/.properties

/etc/CommVaultRegistry/Galaxy/Instance001/CommServe/.properties

 

Best Regards,

Michael

Reply


Terms & ConditionsCookie settings