Support for Commvault 11.40 on Rocky Linux 9.7 or 9.x in general

I just noticed in the release notes of the latest maintenance release an update on this: https://documentation.commvault.com/11.40/software/files/service_pack/updates/11_40_30.htm

Look for: Adding support for Rocky 9 for linux MA - 1308

I would assume this means it is supported in a broader context. 

Based on Arlie:

Yes, Rocky Linux 9.x is a supported operating system for multiple Commvault components and features, including:

• Linux File Servers: Rocky Linux 9.x with glibc 2.34.x is listed as a supported OS for Linux file servers.
  
• 1-Touch and Virtualize Me for Linux: Rocky Linux 9.0–9.5 with glibc 2.34.x is supported.
  
• Ransomware Protection: Rocky Linux 9.x is supported for MediaAgent ransomware protection.
  
• OpenStack VSA Proxy: Rocky Linux 9.x is supported as a platform for Virtual Server Agent proxies in OpenStack environments.
  
   

References:

• System Requirements (compatible) for Linux File Servers
  
• 1-Touch and Virtualize Me for Linux: System Requirements (compatible)
  
• System Requirements (compatible) for Ransomware Protection
  
• OpenStack: System Requirements (compatible)
   

Documentation Links:

• Linux File Servers System Requirements
  
• 1-Touch for Linux System Requirements
  
• Ransomware Protection System Requirements
  
• OpenStack System Requirements

Hi Onno,

Thank you for the quick and detailed answer. I really like the forum’s response time and the depth of its content.

Like in my initial post I’m referencing the following documentation and core components like CommServe. Currently the documentation lists Rocky Linux 8.9 through 9.6.

I would love to see (and technically support) something like Rocky Linux 8.10 through 9.x.

​@commvault0815 the adoption and validation of a new OS version/release can take some time which is pretty common. You can of course raise a CMR/ticket, but in most cases engineer will add support at a certain stage. Right now https://documentation.commvault.com/11.42/commcell-console/commserve_server_system_requirements_linux.html
 

You ask the following:

I would love to see (and technically support) something like Rocky Linux 8.10 through 9.x.

What are you missing because Commvault supports 8.10 all the way up to 9.6. 

Hi ​@Onno van den Berg 

thanks for the input. Since Rocky Linux 9.6 is no longer supported because 9.7 has been released, I would like to see at least 9.7 listed as supported—or, as I mentioned, Rocky Linux 9.x in general.

The issue for us is that when you run a normal update on Rocky Linux 9.6 (which is recommended because backups are part of our critical infrastructure), the system will automatically update to 9.7 or any later release once it becomes officially available.

​@commvault0815 the issue here is somewhat complex, because if you take into account the Commvault perspective they require time to adopt the new minor, which generally means perform a regular update of the OS, and run a Q&A validation test to be able to at least validate if Commvault will keep on running and this takes some time.

The fact that they will always run behind in their documentation in terms of versioning doesn't make it unsupported. Commvault will for sure pick up your ticket in case you run into issues. 

Generally speaking I think Commvault should consider reviewing the current state of the documentation and the OS validation process and rethink how these questions, who come by quite often, can be addressed. 

My recommendation would be to remove all references to specific minor versions from the documentation or replace them with a generic format such as 9.x. Additionally, include a clear statement about official support for minor versions.

I would also suggest improving the Q&A process so that whenever a new minor version is adopted, Commvault automatically updates the support page to inform customers that the Q&A validation has been successfully completed for that version.

​@Damian Andre ​@Sougato Roy can you maybe chip in here are ask someone from engineering to make a comment here? 

​@Onno van den Berg Thank you for flagging this. I’ve reached out to the teams to gather a clear and accurate answer. Please allow me some time to follow up, and I’ll provide an update as soon as I have the full details.

Thanks! 

Roy