Skip to main content

Upgrading HPE 3PAR SRA (Storage Replication Adapter) from 6.1 to 6.5

Here 
are the high level step to upgrade the HPE 3PAR Storage Replication Adapter (SRA) -

    If old SRA is visible in add remove programs - 


    • View certificates for old array (that will be removed after migration) from SRM server using following path and TPDsrm utility -
           C:\Program Files\VMware\VMware Site Recovery manager\Storage\SRA\3Parinsrv>              TPDsrm.exe viewcert
    • Uninstall old 3PAR SRA from SRM server using uninstall program feature.
    • Reboot the SRM server.
    • Install new 3PAR SRA using the .exe file provided by vendor. Check if you can see the new SRA in Program list. If so, reboot the SRM server. 
    • Validate certificates for new array using following path and command on SRM server -
           C:\Program Files\VMware\VMware Site Recovery manager\Storage\SRA\3Parinsrv>              TPDsrm.exe validatecert -sys x.x.x.x -user username -pass ********
    sys - IP address of the new array 
    username - User created on 3PAR array to communicate with VMware SRM
    • Remove the certificates for the old array from SRM server -
           C:\Program Files\VMware\VMware Site Recovery manager\Storage\SRA\3Parinsrv>              TPDsrm.exe removecert -sysID xxxxxx

    xxxxxx - SYSID for old array that was copied from the first step above (Make sure to use the correct one else you will remove the new certs)

    If old SRA is not visible in add remove programs - 


    • View certificates for old array (that will be removed after migration) from SRM server using following path and TPDsrm utility -
           C:\Program Files\VMware\VMware Site Recovery manager\Storage\SRA\3Parinsrv>              TPDsrm.exe viewcert
    • Install Microsoft .net framework on SRM server.
    • Install new 3PAR SRA using the .exe file provided by vendor. Check if you can see the new SRA in Program list. If so, reboot the SRM server. 
    • Validate certificates for new array using following path and command on SRM server -
           C:\Program Files\VMware\VMware Site Recovery manager\Storage\SRA\3Parinsrv>              TPDsrm.exe validatecert -sys x.x.x.x -user username -pass ********
    sys - IP address of the new array 
    username - User created on 3PAR array to communicate with VMware SRM
    • Remove the certificates for the old array from SRM server -
           C:\Program Files\VMware\VMware Site Recovery manager\Storage\SRA\3Parinsrv>              TPDsrm.exe removecert -sysID xxxxxx

    xxxxxx - SYSID for old array that was copied from the first step above (Make sure to use the correct one else you will remove the new certs).









    Comments

    Popular posts from this blog

    How to Check Up Time of ESXi Host or Virtual Machine from vCenter Server

    To check up time of ESXi host from vCenter server - Logon to vCenter Server -  If using C# (fat) client - click on cluster - on right side pane click on Hosts - select the up time option by right clicking on the header. The column will be added at the end. You can drag and drop column to place it in your view. If using HTML client - click on cluster - on right side pane click on Hosts - select the up time attribute from show/hide column by clicking on the header  If using web (Flash)  client - click on cluster - on right side pane click on related objects - hosts - right click on the header to show/hide column - click on up time attribute Similarly,  you can check the up time for a virtual machine by clicking on the virtual machine tab instead of host tab, but only caveat  is vCenter gives you up time of a virtual machine according to reboots performed from the vCenter. So, rather than rebooting server fr...

    VMware NSX Manager Not Showing up in vCenter inventory

    The NSX manager was deployed and configured correctly. It was showing up in vCenter, when I configured it. After few days when I checked suddenly NSX  disappeared from the vCenter inventory. I logged in to NSX manager and it was all fine. It was showing as connected with its respective vCenter but wasn't showing up in the vCenter.  I tried to restart the vCenter services and vCenter server that did not resolve the issue. Easiest fix that worked with me for this issue is to restart the NSX manager and then it shows up back in vCenter.