Skip to main content
Question

Virtual Windows 19 SQL 16 CV 11.28 CommServe with LiveSync Upgrade

  • May 14, 2026
  • 3 replies
  • 35 views

Forum|alt.badge.img+1

I have a VM LiveSync setup, CommServe is Windows 19 running 11.28 and old version of SQL. From the online documentation and the SQL upgrade recommendations, and supported version migration for Windows to Linux. It looks like the hardware refresh and staying on Windows (enabled in REGEDIT) to 11.40 is the best approach, this will allow for the Windows migration to Linux by Dec-2027 approach with supported workflows. Are there any caveats - or a link to VMs (LiveSync) hardware refresh steps, CommServe installed with C-Name, so expecting a straightforward import on to Windows 25 and SQL 22.

It seems because of the old version of CV, stops me running SQL in place upgrades or Windows to Linux migrations. Everything seems to be 11.32. or 11.36 options only, so to avoid multiple convoluted paths, just create 2 x new VM’s, enable CV on Windows and download CV 11.40.x import the CV DB’s during install. Shutdown the old LiveSync pair and fire up the new VM’s importing the DB files during the CV install. Keep it simple to get on a supported version.

Just looking to understand the LiveSync piece and any caveats during install. I presume installing the existing DRServe DB during the standby node install and so on process being advisable. Am i correct in that once on 11.40 a Linux standby server can be added to the mix and is supported, assisting with migration off Windows (this i need to check).

Hope the scenario and thought process makes sense, and nothing obvious, that i’ve missed.


All answers thoughts appreciated.

 

Jules            

3 replies

Forum|alt.badge.img+17
  • Vaulter
  • May 15, 2026

Hi ​@Jules_cb ,

The above scenario and approach are well thought out and align with supported upgrade and migration paths. Here’s a structured summary, with references to the relevant documentation:


1. Current Limitations (Commvault 11.28, Old SQL, Windows)
In-place SQL upgrades and Windows-to-Linux migrations are not supported on 11.28.
Most cross-platform and SQL upgrade workflows require at least 11.32 or 11.36.

2. Recommended Path: Hardware Refresh on Windows, Upgrade to 11.40
Upgrade to 11.40 on Windows first. This is the best way to unlock supported migration and upgrade workflows.

You can perform a hardware refresh to new Windows VMs (e.g., Windows Server 2022/2025) and SQL 2022, using the DR backup/import method.

LiveSync: After the hardware refresh and upgrade, you can re-enable LiveSync between the new VMs.

Documents for ref:
https://documentation.commvault.com/2023e/commcell-console/commserve_hardware_refresh_preparing_new_hardware.html - Hardware refresh.

https://documentation.commvault.com/11.40/software/upgrading_microsoft_sql_server_editions_on_commserve_computer.html - SQL upgrade.

 

Recommended steps:

  1. Build two new Windows VMs (production and standby).
  2. Install Commvault 11.40 on the production VM, using the DR backup from the old environment.
  3. Install the standby node (pointing to the production node during install).
  4. Enable LiveSync between the two new VMs.

Forum|alt.badge.img+1
  • Author
  • Novice
  • May 15, 2026

thank you Pradeep for the clear walk through, i haven’t check on adding the Linux Standby server, post refresh, did you know if this was supported moving forward for failover testing.

 

cheers


Jules  


Forum|alt.badge.img+17
  • Vaulter
  • May 15, 2026

Hi ​@Jules_cb ,
 

Cross-platform (Linux to Windows or Windows to Linux) LiveSync is supported, but there are important requirements and limitations.

  • Cross-Platform Flexibility: In mixed OS setups (e.g., Windows production CommServe and Linux standby CommServe), the OS versions do not need to match. Any Commvault-supported OS version for each platform can be used.
  • SQL Server Port Limitation (Linux): CommServe LiveSync on Linux does not support SQL Server running on a non-default port (must use port 1433). Using a custom port will cause LiveSync configuration to fail. This limitation is planned to be addressed in a future release (expected in version 11.44 or later).