Forum Discussion

sriramrane's avatar
sriramrane
Level 4
4 years ago

Enterprise Vault 12.1 Migration from VCS to Windows 2019 Failover Cluster

Hello Dears,

One of client of ours planning to migrate the Enterprise Vault from VCS to Windows Server Failover Cluster 

Current Setup:  EV 12.1 on Veritas Cluster installed on Windows 2016 

Planned New Setup: EV 14.x on Microsoft Windows 2019 Failover Cluster

I have tried to search the KB articles on Veritas, but haven't got any article which mentions the cross cluster migration for EV.

In past have done many EV Cluster Migration between VCS-to-VCS and WSFC-to-WSFC using EV Cluster Migration Wizard, but not cross cluster migration.  

Very much appreciate, if anyone can give valuable expertised guidance here

 

Regards,

Rane

  • GertjanA's avatar
    GertjanA
    4 years ago

    Hello Rane, 

    If you download the SSMW, and read the PDF, you come across information in regards to Clustering. See below. 

    Quote : "Migrating clustered servers.
    You can use the Enterprise Vault Server Settings Migration wizard to create migration packages for clustered Enterprise Vault servers. When you have created the migration packages you can then import them on clustered servers or on standalone servers.
    When you create a migration package on a clustered server then import it on a standalone server, the Server Settings Migration wizard warns that the clustering configuration of the source and target servers are different, but you can continue with the import.

    If you migrate clustered source servers to clustered target servers, refer to the Enterprise Vault documentation which contains the information you need to configure prerequisites and install Enterprise Vault in a cluster.
    During the deployment of the new cluster, you can attach to the target servers the data locations that were used by the source servers, with the following exceptions:
    1 - In both Microsoft Cluster Services and Veritas Cluster Services, you must create a new data location for the MSMQ queues. Do not attempt to use the MSMQ data location that was attached to the source servers.
    2 - In Veritas Cluster Services, you must create a new data location for the RegRep resource. Do not attempt to use the RegRep data location that was attached to the source servers.

    " END QUOTE.

    It should therefor be possible...

     

    • sriramrane's avatar
      sriramrane
      Level 4

      Hi Gertjan,

      I too don't have experience in EV Cross-Cluster migrations. I was wondering what cluster information the EV SSMW carries while exporting. Any VCS information along with VxVM in the export will be irrational to Windows Failover Cluster. if anyone tried and tested from VCS to WSFC will give better idea on what challenges came across during migration. 

      Other possible approach can be, Migrate to standalone node and then run HA configurations on Windows Failover Cluster and then add up additional nodes to cluster. Never done this, but look like this is possible, in case EV SSMW is not able to migrate between VCS & WSFC.

      Your suggestions will be highly appreciated.

       

      Regards.

      Rane

       

      • GertjanA's avatar
        GertjanA
        Moderator

        Hello Rane, 

        If you download the SSMW, and read the PDF, you come across information in regards to Clustering. See below. 

        Quote : "Migrating clustered servers.
        You can use the Enterprise Vault Server Settings Migration wizard to create migration packages for clustered Enterprise Vault servers. When you have created the migration packages you can then import them on clustered servers or on standalone servers.
        When you create a migration package on a clustered server then import it on a standalone server, the Server Settings Migration wizard warns that the clustering configuration of the source and target servers are different, but you can continue with the import.

        If you migrate clustered source servers to clustered target servers, refer to the Enterprise Vault documentation which contains the information you need to configure prerequisites and install Enterprise Vault in a cluster.
        During the deployment of the new cluster, you can attach to the target servers the data locations that were used by the source servers, with the following exceptions:
        1 - In both Microsoft Cluster Services and Veritas Cluster Services, you must create a new data location for the MSMQ queues. Do not attempt to use the MSMQ data location that was attached to the source servers.
        2 - In Veritas Cluster Services, you must create a new data location for the RegRep resource. Do not attempt to use the RegRep data location that was attached to the source servers.

        " END QUOTE.

        It should therefor be possible...