Skip to main content

Good day all

I was trialling the V11.40 SDK today, but notice that the Commserve Role doesn’t appear to be part of the Media Kit yet. Has anyone else experienced this?

 

I also notice that V11.40 is not yet available on the Store.

Hi ​@Mauro,

Two things:

  1. Download

When accessing store.commvault.com - hit the login button and login with your Commvault credentials and let me know if you see the LTS 11.40 release then?

Workaround: download from the support portal: https://support.commvault.com/ESD?fv=11.0

  1. CommServe - There was discussion about deprecating NEW Windows-based CommServe deployments in 11.40 to encourage the inherently more secure Linux platform. I don’t see it documented, so let me double check if this occurred.

    Update: The above is true - docs in the process of being updated to reflect the change.

 


Hi ​@Mauro,

Two things:

  1. Download

When accessing store.commvault.com - hit the login button and login with your Commvault credentials and let me know if you see the LTS 11.40 release then?

Workaround: download from the support portal: https://support.commvault.com/ESD?fv=11.0

  1. CommServe - There was discussion about deprecating NEW Windows-based CommServe deployments in 11.40 to encourage the inherently more secure Linux platform. I don’t see it documented, so let me double check if this occurred.

    Update: The above is true - docs in the process of being updated to reflect the change.

 

Thanks very much for this update. So with CV looking to move away from the Windows platform, it appears that you can’t deploy a new instance of a Commserve on Windows. You need to install the previous version and then run the upgrade. Even doing it this way does not show you the Commserve Component as being available. I am testing the upgrade and will provide some updates soon.

 

 


So it seems you cannot use this package to upgrade a Commserve instance on a Windows OS. 
It seems to uninstall the Commserve Components and doesn’t re-add them.

The Commvault services fail to start too. 

 

Installing V11.40 on a Linux server has all the Commserve components.

I could be wrong here, but I think this may be a premature feature release with no documentation. If a customer decided to upgrade this without the documentation being updated, they will sit with a broken Commserve. I also am curious if the limitations of a Commserve on Linux have been addressed with this new release.
 

 


I do not have an FR36, but I did upgrade a Windows FR38 to FR40 without issue.
 


Thanks,
Scott
 


I do not have an FR36, but I did upgrade a Windows FR38 to FR40 without issue.
 


Thanks,
Scott
 

V11.36 to V11.40 doesn’t seem happy. I’ll try V11.38 to V11.40 and report back.


Hi all

 

So I’ve done a bit of testing and can confirm the below.

V11.38 will upgrade to V11.40 with full functionality.

V11.36 will not upgrade to V11.38 or to V11.40. The audit service fails to install and the installation breaks.

 

I need to do a bit more reading, but it’s safe to say that V11.40 the replacement for V11.38 and all it’s features.

So my two observations are as follows:

  1. As a new install, V11.40 does not include the Commserve components for a Windows hosted Commserve.
  1. It doesn’t seem to be compatible as an as an upgrade route from V11.36.

 

I’ll do a bit more research and hopefully a little more info is shared soon on this.

 

Thanks,

Mauro


Starting with Commvault version 11.40, new installations of Windows-based CommServe (and potentially WebServer) components are no longer supported. However, existing installations on Windows can still be upgraded to version 11.40 without any issues.


What happens when I need to perform a hardware refresh?


What happens when I need to perform a hardware refresh?

This is where I envision some potential issues. It seems that you either switch to a Linux OS or install an older version of Commvault and then upgrade to V11.40.

It seems that going forward you’re forced to change host OS platforms, but let’s see if any further info comes though from Commvault.


Reply