Validate Supported Procedure for Separating CommServe and MediaAgent After Upgrade to 11.40

We currently have a self-hosted Commvault environment running version 11.36.

The CommServe and MediaAgent are installed on the same physical Windows server. The same server also hosts the existing MediaAgent components, including the DDB, Index Cache, Disk Libraries, Mount Paths, Data Paths.

The customer’s main requirements are:

• Minimum operational risk
• Minimum downtime
• No unnecessary CommServe name or IP updates on the clients
• The existing physical server must remain in service as the MediaAgent after the separation

Our planned approach is to first upgrade the existing combined CommServe/MediaAgent server from 11.36 to the latest approved 11.40 Maintenance Release.

The upgrade and the separation will be performed as two separate changes, with a stabilization and validation period between them.

Planned Final Architecture

New virtual server:

• CommServe only
• Receives the original CommServe hostname
• Receives the original CommServe IP address

Existing physical server:

• Remains as the MediaAgent
• Receives a new hostname
• Receives a new IP address
• Continues using the existing DDB, Index Cache, Libraries, Mount Paths, and storage connectivity

Planned Upgrade Phase

1. Validate Windows Server, SQL Server, MediaAgent, client, and storage compatibility with 11.40.
2. Prepare the required Commvault installation media and updates in advance.
3. Complete a successful CommServe DR backup and copy the DR set to an external location.
4. Validate the DDB status, DDB backup, Index Cache, Libraries, Mount Paths, and Data Paths.
5. Upgrade the combined CommServe/MediaAgent server from 11.36 to 11.40.
6. Upgrade the required MediaAgents and infrastructure components.
7. Perform backup, restore, Auxiliary Copy, tape, DDB, and DR backup validation.
8. Allow the environment to operate normally and confirm stability before starting the separation activity.

Planned Separation Phase

Based on the updated 11.40 documentation, our understanding is that the supported process is:

1. Enable multi-instance installation on the existing combined server.
2. Install a new MediaAgent as Instance002 on the same physical server, using a temporary CommCell client name.
3. Move or reassociate the existing DDBs to the MediaAgent running under Instance002.
4. Move or reconfigure all Disk Libraries, Tape Libraries, Mount Paths, Drive Pools, and Data Paths to use Instance002.
5. Copy or relocate the Index Cache as required.
6. Validate that backup, restore, Auxiliary Copy, tape operations, and DDB operations work through Instance002.
7. Perform a final CommServe DR backup.
8. Stop CommCell activities.
9. Remove Instance001, which currently contains the CommServe and the original MediaAgent installation.
10. Rename and re-IP the physical server using its final MediaAgent hostname and IP address.
11. Rename and re-IP the prepared virtual server using the original CommServe hostname and IP address.
12. Install or recover the CommServe on the new virtual server using the final DR backup.
13. Update the temporary MediaAgent identity in the CommCell so it matches the final hostname of the physical MediaAgent.
14. Validate all MediaAgents, DDBs, Libraries, Data Paths, clients, backups, restores, Auxiliary Copies, tape operations, and DR backups.

The objective of retaining the original CommServe hostname and IP address is to avoid updating the CommServe identity across all clients and to reduce firewall, DNS, and communication changes.

Could you please confirm the following?

1. Is this still the correct and fully supported procedure in Commvault 11.40?
2. Is installing the replacement MediaAgent as Instance002 on the original physical server the recommended approach for this scenario?
3. Can the existing DDB, Index Cache, Disk Libraries, Mount Paths, and tape configuration remain on the same physical server when it is converted to a MediaAgent-only server?
4. Are there any additional steps required in 11.40 before uninstalling Instance001?
5. Should the new CommServe be installed directly with the original hostname and IP before the DR recovery, or is there a different recommended sequence?
6. Is there any risk in changing the operating system hostname and IP of the physical server after the MediaAgent roles have been moved to Instance002?
7. Are additional licenses required temporarily for the second MediaAgent instance?
8. Are there any known limitations, registry settings, Name Management operations, certificate considerations, SQL requirements, or firewall changes specific to 11.40?
9. Is it recommended to involve Commvault Support before removing Instance001, even after all MediaAgent validation tests have completed successfully?
10. Is there a newer or lower-risk method available in 11.40 that would avoid the multi-instance and server rename process?

We would appreciate confirmation from anyone who has successfully completed this procedure on version 11.40.