Skip to main content
commvault.com commvault.com
Solved

In-place Windows Server 2016 to 2025 upgrade on a physical Commvault All-in-One server running 11.40.67

  • September 9, 2026
  • 3 replies
  • 55 views
Apprentice
Forum|alt.badge.img+7

Hello,

We are planning an operating system upgrade for a physical Commvault All-in-One server and would like to hear from anyone who has completed a similar upgrade.

Current configuration:

  • Physical Cisco UCS C240 M5 server
  • Windows Server 2016 Standard
  • Commvault 11.40.67
  • Non-clustered CommServe
  • The same server hosts the CommServe, MediaAgent, Web Server/Command Center and Workflow Engine components
  • Local DDBs and disk-library mount paths are also hosted on this server
  • The customer does not want to split the CommServe and MediaAgent roles or migrate them to new hardware

The planned target is an in-place upgrade directly from Windows Server 2016 to Windows Server 2025.

Microsoft supports the direct upgrade path for a non-clustered server, and Commvault 11.40 supports Windows Server 2025. However, the exact procedure for an All-in-One server is not fully clear, especially because the same machine hosts both the CommServe and MediaAgent roles.

I would appreciate feedback on the following:

  1. Has anyone successfully completed a direct Windows Server 2016 to Windows Server 2025 in-place upgrade on a physical Commvault All-in-One server?
  2. Is the direct 2016 to 2025 upgrade recommended for this configuration, or would a staged upgrade through Windows Server 2022 be safer?
  3. What is the recommended shutdown order when the CommServe and MediaAgent are installed on the same server?
  4. Should we disable CommCell activities, MediaAgent operations, libraries and data paths before stopping the Commvault services?
  5. Should the Commvault Windows File System package remain installed during the OS upgrade? The documentation mentions seamless OS upgrades for CommServe and MediaAgent components, but the generic Windows File System guidance appears to suggest uninstalling and reinstalling agent software.
  6. Are there any known issues involving SQL Server 2022, IIS, Tomcat, MongoDB, DDB/SIDB processes, local disk-library mount paths, Cisco VIC drivers or RAID controller drivers after the OS upgrade?
  7. For rollback, should we rely on a CommServe DR recovery and server rebuild, or is the Windows in-place upgrade rollback considered a valid recovery option?

Before the upgrade, we plan to:

  • Create and validate a new CommServe DR backup stored outside this server
  • Perform and validate DDB backups
  • Confirm that all DDBs and disk-library mount paths are healthy
  • Stop or complete all active jobs
  • Disable data protection and recovery activities
  • Disable the MediaAgent and its libraries
  • Confirm that SIDB.exe and SIDB2.exe are no longer running
  • Document the network configuration, drive letters, mount paths, service accounts and hardware driver versions
  • Verify Cisco UCS firmware and Windows Server 2025 driver compatibility

Are there any additional prerequisites or All-in-One-specific steps that should be included?

Thank you.

Best answer by Jean-Paul

Hi all,

Just wanted to close the loop and share the outcome of the upgrade, as this may help others considering a similar path.

Environment:

  • Commvault version: 11.40.67
  • Main server: physical CommServe + MediaAgent on the same server
  • OS before upgrade: Windows Server 2016
  • Target OS: Windows Server 2025 Datacenter
  • Additional MediaAgent: virtual server
  • VMware VSA / Access Node: virtual server

We decided to proceed with an in-place OS upgrade from Windows Server 2016 directly to Windows Server 2025.

Before the upgrade we performed the following:

  • Verified that no backup/restore jobs were running.
  • Ran a fresh CommServe DR backup and copied the DR backup set to an external network location.
  • Ran fresh DDB backups.
  • Verified the DDB status and free space.
  • Verified disk libraries and mount paths.
  • Reviewed the physical RAID health through Cisco CIMC.
  • Verified that both the RAID1 boot volume and RAID5 data volume were healthy and optimal.
  • Documented the NIC configuration, IP addresses, gateways, DNS settings and static routes.
  • Documented the existing NIC Teams on the physical CommServe.
  • Disabled CommCell activity and MediaAgent activity before stopping the services.
  • Stopped all Commvault services using Process Manager.
  • For the virtual MediaAgent and VSA, we shut down the VMs and created VMware snapshots before the OS upgrade.

The physical CommServe/MediaAgent was upgraded first.

Upgrade path:

  • Windows Server 2016 Standard
  • Direct in-place upgrade
  • Windows Server 2025 Datacenter (Desktop Experience)
  • "Keep files, settings, and apps"

The upgrade completed successfully.

After the upgrade we verified:

  • Windows Server 2025 Datacenter was running correctly.
  • Hostname and domain membership were preserved.
  • Network configuration, NIC Teaming, IP addresses and routes were preserved.
  • All local disks and drive letters were preserved.
  • Cisco RAID controller and both Virtual Drives remained Optimal.
  • Commvault services started successfully.
  • CommServe version remained 11.40.67.
  • All installed Commvault packages showed Up To Date.
  • Jerusalem DDBs were Online.
  • Jerusalem disk library and all five mount paths were Ready / ReadWrite.

We then upgraded the virtual MediaAgent to Windows Server 2025 Datacenter using the same in-place upgrade method.

After the MediaAgent upgrade:

  • DDB and Index disks were available with the same drive letters.
  • Disk library mount path returned to Ready / ReadWrite.
  • One DDB came back Online immediately.
  • The second DDB initially showed "Resync scheduled".
  • Commvault performed the DDB recovery/resync automatically.
  • After the resync completed, the DDB returned to Online with Offline Reason = N/A.
  • An Index Server backup through this MediaAgent completed successfully.

Finally, we upgraded the VMware VSA / Access Node to Windows Server 2025 Datacenter.

After the VSA upgrade:

  • The server came back online normally.
  • Commvault Virtual Server package was present.
  • vCenter communication worked.
  • VM inventory preview worked successfully and returned the expected VM inventory.

We could not perform an immediate test VM backup because the environment was inside a backup blackout window, but the VSA connectivity and inventory discovery were validated successfully.

Final result:

  • CommServe + MediaAgent: Windows Server 2025 Datacenter - successful
  • Virtual MediaAgent: Windows Server 2025 Datacenter - successful
  • VMware VSA / Access Node: Windows Server 2025 Datacenter - successful
  • Commvault remained on 11.40.67
  • DDBs Online
  • Libraries Ready / ReadWrite
  • Post-upgrade Commvault jobs completed successfully

The main observation from our side was the DDB resync after the virtual MediaAgent upgrade. We did not force a reconstruction or manually intervene. We allowed Commvault to complete the scheduled resync, after which the DDB returned to Online normally.

Thanks again to everyone who shared recommendations, especially the suggestions around DR backup, disabling activity before shutdown, and considering the rollback options. In our case, the direct Windows Server 2016 to Windows Server 2025 in-place upgrade completed successfully.

 

Of course, this is only our specific environment and result. I would still recommend validating the exact Commvault release, hardware/driver compatibility and rollback plan before using the same upgrade path in another environment.

3 replies

Apprentice
Forum|alt.badge.img+7
  • Jean-PaulApprentice
  • Author
  • Apprentice
  • September 9, 2026

Microsoft officially supports a direct in-place upgrade to Windows Server 2025 from Windows Server 2012 R2 and later. Therefore, Windows Server 2016 to Windows Server 2025 is a supported Microsoft upgrade path.

From a Commvault supportability and field-experience perspective, is the direct upgrade recommended for a physical All-in-One server running 11.40.67, or would Commvault recommend a staged upgrade through Windows Server 2022?

Vaulter

Hi ​@Jean-Paul 

  1. Can’t comment on Q1 as I didn’t go through this upgrade before myself.
  2. Is the direct 2016 to 2025 upgrade recommended for this configuration, or would a staged upgrade through Windows Server 2022 be safer?
  3. What is the recommended shutdown order when the CommServe and MediaAgent are installed on the same server?
    • Make sure no jobs are running, put All MAs (including CS one) in maintenance mode, disable all activity on the CommCell, and finally open CV process manager, right click on “All Services” → stop
  4. Should we disable CommCell activities, MediaAgent operations, libraries and data paths before stopping the Commvault services?
    • Yes, recommended precaution
  5. Should the Commvault Windows File System package remain installed during the OS upgrade? The documentation mentions seamless OS upgrades for CommServe and MediaAgent components, but the generic Windows File System guidance appears to suggest uninstalling and reinstalling agent software.
    • File System Agent must be installed all the time on the commserve
  6. Are there any known issues involving SQL Server 2022, IIS, Tomcat, MongoDB, DDB/SIDB processes, local disk-library mount paths, Cisco VIC drivers or RAID controller drivers after the OS upgrade?
    • This is a very general question, OS upgrade and compatability issues with the mentioned 3rd parties should be a answered by Microsoft or the 3rd party involved, from Commvault prespective, please refer to the known issues documentation and HotFixes page for the respective CV version
  7. For rollback, should we rely on a CommServe DR recovery and server rebuild, or is the Windows in-place upgrade rollback considered a valid recovery option?
    • Those are two different options and both of them should be valid.

I hope this helps,

Thanks,

Abdu

linkedin.com/in/alsindiony-abdo
Apprentice
Forum|alt.badge.img+7
  • Jean-PaulApprentice
  • Author
  • Apprentice
  • Answer
  • September 23, 2026

Hi all,

Just wanted to close the loop and share the outcome of the upgrade, as this may help others considering a similar path.

Environment:

  • Commvault version: 11.40.67
  • Main server: physical CommServe + MediaAgent on the same server
  • OS before upgrade: Windows Server 2016
  • Target OS: Windows Server 2025 Datacenter
  • Additional MediaAgent: virtual server
  • VMware VSA / Access Node: virtual server

We decided to proceed with an in-place OS upgrade from Windows Server 2016 directly to Windows Server 2025.

Before the upgrade we performed the following:

  • Verified that no backup/restore jobs were running.
  • Ran a fresh CommServe DR backup and copied the DR backup set to an external network location.
  • Ran fresh DDB backups.
  • Verified the DDB status and free space.
  • Verified disk libraries and mount paths.
  • Reviewed the physical RAID health through Cisco CIMC.
  • Verified that both the RAID1 boot volume and RAID5 data volume were healthy and optimal.
  • Documented the NIC configuration, IP addresses, gateways, DNS settings and static routes.
  • Documented the existing NIC Teams on the physical CommServe.
  • Disabled CommCell activity and MediaAgent activity before stopping the services.
  • Stopped all Commvault services using Process Manager.
  • For the virtual MediaAgent and VSA, we shut down the VMs and created VMware snapshots before the OS upgrade.

The physical CommServe/MediaAgent was upgraded first.

Upgrade path:

  • Windows Server 2016 Standard
  • Direct in-place upgrade
  • Windows Server 2025 Datacenter (Desktop Experience)
  • "Keep files, settings, and apps"

The upgrade completed successfully.

After the upgrade we verified:

  • Windows Server 2025 Datacenter was running correctly.
  • Hostname and domain membership were preserved.
  • Network configuration, NIC Teaming, IP addresses and routes were preserved.
  • All local disks and drive letters were preserved.
  • Cisco RAID controller and both Virtual Drives remained Optimal.
  • Commvault services started successfully.
  • CommServe version remained 11.40.67.
  • All installed Commvault packages showed Up To Date.
  • Jerusalem DDBs were Online.
  • Jerusalem disk library and all five mount paths were Ready / ReadWrite.

We then upgraded the virtual MediaAgent to Windows Server 2025 Datacenter using the same in-place upgrade method.

After the MediaAgent upgrade:

  • DDB and Index disks were available with the same drive letters.
  • Disk library mount path returned to Ready / ReadWrite.
  • One DDB came back Online immediately.
  • The second DDB initially showed "Resync scheduled".
  • Commvault performed the DDB recovery/resync automatically.
  • After the resync completed, the DDB returned to Online with Offline Reason = N/A.
  • An Index Server backup through this MediaAgent completed successfully.

Finally, we upgraded the VMware VSA / Access Node to Windows Server 2025 Datacenter.

After the VSA upgrade:

  • The server came back online normally.
  • Commvault Virtual Server package was present.
  • vCenter communication worked.
  • VM inventory preview worked successfully and returned the expected VM inventory.

We could not perform an immediate test VM backup because the environment was inside a backup blackout window, but the VSA connectivity and inventory discovery were validated successfully.

Final result:

  • CommServe + MediaAgent: Windows Server 2025 Datacenter - successful
  • Virtual MediaAgent: Windows Server 2025 Datacenter - successful
  • VMware VSA / Access Node: Windows Server 2025 Datacenter - successful
  • Commvault remained on 11.40.67
  • DDBs Online
  • Libraries Ready / ReadWrite
  • Post-upgrade Commvault jobs completed successfully

The main observation from our side was the DDB resync after the virtual MediaAgent upgrade. We did not force a reconstruction or manually intervene. We allowed Commvault to complete the scheduled resync, after which the DDB returned to Online normally.

Thanks again to everyone who shared recommendations, especially the suggestions around DR backup, disabling activity before shutdown, and considering the rollback options. In our case, the direct Windows Server 2016 to Windows Server 2025 in-place upgrade completed successfully.

 

Of course, this is only our specific environment and result. I would still recommend validating the exact Commvault release, hardware/driver compatibility and rollback plan before using the same upgrade path in another environment.

Readiverse Academy Certifications

description of image
Terms & ConditionsAccessibility statement