Skip to main content

Current version(s):

Server Name: snappro01
    - SQL Server 2012 on dca-h-snappro01.int.dca.ca.gov
    - CommVault 2022E 11.28
    
Needed version(s):

- Server Name: snappro02
    - SQL Server 2019 on dca-h-snappro01.int.dca.ca.gov
    - CommVault 2023E 11.32

 

Please see the attachment for the upgrade instructions that I am closely following.

 

Based on these instructions, you would normally be installing the new platform (2023E) to the same server that once hosted the old software (2022E). Moreover, by submitting the DR backup file, all of the old setting and metadata would transfer over.

 

However, our current virtual server that hosts 2022E does not have the necessary system requirements to host 2023E. Therefore, our goal is to create a new virtual server, install all necessary commserve software, and have this be associated as our new snappro server (snappro02).

 

Questions:

  1. Does the commserve and sql software still have to be deleted from the old server (snappro01)? Or can we keep this server and disassociate it in favor of the new server?
  2. When installing the Commserve software onto the new server (snappro02), will submitting the DR file still work even though it is associated with the old server (snappro01)?

 

Hi @lj_dca24 ,

 

We have documentation for what you are trying to achieve, it is call a “Hardware Refresh”, check this out;

 

https://documentation.commvault.com/2023e/expert/commserve_hardware_refresh_overview.html


Hi @lj_dca24 ,

 

We have documentation for what you are trying to achieve, it is call a “Hardware Refresh”, check this out;

 

https://documentation.commvault.com/2023e/expert/commserve_hardware_refresh_overview.html

 

Thank you for this.

The doc states that it is possible to use the same computer host name and IP settings.

Would it be possible to perform the hardware refresh with a different host name and the same IP settings?


As long as the DNS Server is pointing to the correct IP Address it should be fine.

You may need to keep a CName for the old hostname pointing to the IP so any Client configured to reach the CS by its hostname is still able to do so


Reply