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:
- Has anyone successfully completed a direct Windows Server 2016 to Windows Server 2025 in-place upgrade on a physical Commvault All-in-One server?
- Is the direct 2016 to 2025 upgrade recommended for this configuration, or would a staged upgrade through Windows Server 2022 be safer?
- What is the recommended shutdown order when the CommServe and MediaAgent are installed on the same server?
- Should we disable CommCell activities, MediaAgent operations, libraries and data paths before stopping the Commvault services?
- 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.
- 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?
- 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.
