Skip to main content
Question

New installation Commserver on Linux

  • March 31, 2026
  • 18 replies
  • 168 views

Forum|alt.badge.img+17

I would like to deploy a new CommServe server on Linux using SP 11.40. My current CommServe is running on Windows with SP 11.36. I plan to set up the new CommServe as a standby node in advance.

Could you advise on the best practices for this setup?

The operating system I am using is Rocky Linux. I have provisioned an additional disk for the Commvault installation and software cache, which is mounted at /opt/CommvaultData.

What are the initial steps I should follow to ensure a secure and reliable installation?

 

For the installation of SP 11.40, I would like to first deploy two new passive nodes on Linux, and only then perform the failover to Linux.

I also have a question regarding the software cache. With the new CommServe on Linux, I have configured a new software cache for Windows and enabled it as a remote software cache.

How can I ensure that, during update installations, clients automatically use the correct remote cache? Specifically, I want Windows clients to use the Windows software cache and Linux clients to use the Linux software cache.

 

I have already created two new client groups, categorized into Linux clients and Windows clients.

18 replies

Forum|alt.badge.img+18
  • Vaulter
  • April 1, 2026

Here is the documentation to migrating from Windows CS to Linux CS:
https://documentation.commvault.com/11.40/software/performing_commserve_migration_from_windows_to_linux.html

You should be able to set which cache to use from the properties of the client or the client group.


Forum|alt.badge.img+17
  • Author
  • Challenger
  • April 3, 2026

@Orazan 

 

That’s also what I’m working on . I’m doing scenario 3, but I’m getting stuck on the installation of the database and the permissions on the installation folder. The root has full permissions on the folder. I also tried granting MSSQL permissions, but it still doesn’t proceed


Forum|alt.badge.img+17
  • Author
  • Challenger
  • April 13, 2026

@Orazan 

 

"Every time I install the CommServe DB, I run into a problem with permissions on the installation folder. The installation changes the permissions to the Commvault group, but that group does not exist, and then the installation fails when creating the DB2 database."

 

If I change the permissions to mssql:mssql with 775, then when starting the installation it changes back to the Commvault group. Adding the mssql user to the Commvault group does not help either."


Scott Moseman
Vaulter
Forum|alt.badge.img+23

I might suggest a Support case to have it reviewed.  It sounds like it’s not creating the necessary Unix group.  I have installed several Linux CommServes and have not run into this issue.


Thanks,
Scott
 


Forum|alt.badge.img+17
  • Author
  • Challenger
  • April 14, 2026

@Scott Moseman 

 

I am already working with Commvault support, but they are also unable to resolve it. Every time the installation fails, I have to manually reset the permissions. Up to the point of creating the DB2 it works, but after that, with every change in permissions, the installation sets it back again.


Forum|alt.badge.img+17
  • Author
  • Challenger
  • April 14, 2026

@Scott Moseman Did you installed on RockyLinux aswell? Or the linux OS does not matter alot. 


Scott Moseman
Vaulter
Forum|alt.badge.img+23

Typically I use RHEL, but I just tested on Rocky 9, too. No problems.

# cat /etc/redhat-release
Rocky Linux release 9.7 (Blue Onyx)

# commvault status | grep -E '^ Version|1020'
 Version = 11.40.42
 1020/CVGxCommServe = CommServe

Thanks,
Scott
 


Forum|alt.badge.img+17
  • Author
  • Challenger
  • April 15, 2026

@Scott Moseman 

 

Maybe it's because I’m trying to install version 11.36.94 on Linux instead of 11.40? Currently we are using Windows OS as the CommServe, and I wanted to install a passive Linux setup before we move to 11.40."


Scott Moseman
Vaulter
Forum|alt.badge.img+23

FR36 should work fine on both RHEL and Rocky, too.

Support was unable to find the problem?  What do you mean when you say you have to reset the permissions?

Thanks,
Scott
 


Forum|alt.badge.img+17
  • Author
  • Challenger
  • April 15, 2026

@Scott Moseman 

Every time I run the database installation, it does not work on the first attempt. I then have to manually change the ownership with chown mssql:mssql /path, and after that it works. This also happens when the folders /commvaultDB/Commserv and DM2 are created—I have to manually set the ownership there to mssql:mssql as well. But after that, when creating the DM2 database, it does not work. The installation set the permissions to root:commvault with-rw-r. I can also upload the installation log

 

 


Forum|alt.badge.img+17
  • Author
  • Challenger
  • April 20, 2026

@Scott Moseman The issue seems to be when i am trying to install on mounted path, i am made clean installation on OS partition and its seems to be working


Scott Moseman
Vaulter
Forum|alt.badge.img+23

@Scott Moseman The issue seems to be when i am trying to install on mounted path, i am made clean installation on OS partition and its seems to be working


That’s interesting.  I didn’t know that would make a difference.

Thanks,
Scott
​​​​​​​


Forum|alt.badge.img+17
  • Author
  • Challenger
  • April 20, 2026

@Scott Moseman 

Can you also try in your own environment to install the CommServe on a separate disk?


Scott Moseman
Vaulter
Forum|alt.badge.img+23

What kind of mount path? CIFS? NFS?

Thanks,
Scott
 


Forum|alt.badge.img+17
  • Author
  • Challenger
  • April 20, 2026

@Scott Moseman 

 

No juist normaals extra vm disk, 


  • Novice
  • April 21, 2026

Have you checked if you have issues with SELINUX? We does the migration to a RHEL Server and also run into some SELinux Problems.


Forum|alt.badge.img+17
  • Author
  • Challenger
  • April 21, 2026

@nkopf No it is disabled.


Scott Moseman
Vaulter
Forum|alt.badge.img+23

Interesting.  When I mount /opt on a 2nd VM disk, my SQL install failed.

/opt on /dev/vdb1

5424 139816341227072 04/20 19:32:17 ###  @@@ Configuring Microsoft SQL Server ...

5424 139816341227072 04/20 19:32:17 ###  Executing:

MSSQL_SA_PASSWORD='*****' MSSQL_PID=standard MSSQL_AGENT_ENABLED=true /opt/mssql/bin/mssql-conf -n setup accept-eula [GALAXY_INST=Instance001]

5424 139816341227072 04/20 19:32:17 ###  output = /bin/bash:

/opt/mssql/bin/mssql-conf: Permission denied , retcode = 126

5424 139816341227072 04/20 19:32:17 ###  *** Failed Configuring Microsoft SQL Server.

5424 139816341227072 04/20 19:32:17 ###  >>>CALL tasks_error_callback ((Command(<configure_mssql ()>),), {'errorMessage': 'Failed Configuring Microsoft SQL Server'})


/opt on default LVM

# commvault status | grep Home

  Home Directory = /opt/commvault/Base

I would not have expected a 2nd VM disk to be any different.  There must be something different about how it’s getting mounted at the OS level.  I’m mounting it with the defaults in fstab, and the permissions on /opt look the same as far as I can tell.  Weird.

Thanks,
Scott
 


Forum|alt.badge.img+17
  • Author
  • Challenger
  • April 21, 2026

@Scott Moseman 

 

That is indeed interesting. I haven't mounted the /opt on another LV, but only the folder located on the /opt. However, apparently it doesn't matter; it doesn't work for you either, and the error message appears when creating the database?