Transition from CommServe non-clustered to Microsoft OS Clustered

Last post 06-20-2019, 4:01 AM by Wwong. 3 replies.
Sort Posts: Previous Next
  • Transition from CommServe non-clustered to Microsoft OS Clustered
    Posted: 06-13-2019, 5:16 PM

    Hello All,

    I have a Commserve non-cluster that has the following information.

    CommServe Client Name: Friday-CS

    CommServe server hostname: Friday.history.eu

    CommServe IP: 192.168.0.66

    I will move this structure to a Microsoft OS Cluster. I will install MSSQL on a newly installed Microsoft OS Cluster using the following steps.

    https://documentation.commvault.com/commvault/v11_sp13/article?p=1728.htm

    Then I will do DR Restore by following the steps below.

    https://documentation.commvault.com/commvault/v11_sp13/article?p=4788.htm

    My question is: where do I use the client name, hostname and ip information I used before?

    or

    Is it enough to move the currently structure in the Microsoft OS Cluster structure by the following document?

    https://documentation.commvault.com/commvault/v11_sp13/article?p=5025.htm

  • Re: Transition from CommServe non-clustered to Microsoft OS Clustered
    Posted: 06-19-2019, 12:52 AM

    Hi Omer 

    In regards to setting up - Microsoft Failover Cluster Environment, the associated Documentation (https://documentation.commvault.com/commvault/v11_sp13/article?p=5025.htm) is correct.

    From Commvault their should be a single Client, which will resolve to the client name, hostname and ip information. Then the Microsoft OS Cluster will manage which Host is online and which one should be offline.

    Regards

    Winston  

  • Re: Transition from CommServe non-clustered to Microsoft OS Clustered
    Posted: 06-19-2019, 2:59 AM

    Hi Winston,

    Thank you for your reply. First of all what do you mean by saying "From Commvault their should be a single client" ? Could you explain it more ?

    Secondly, from the following documentation on the step 7, which one is referred Client name and FQDN name from section b and c ?

    https://documentation.commvault.com/commvault/v11_sp13/article?p=5025.htm

    Best Regards.

  • Re: Transition from CommServe non-clustered to Microsoft OS Clustered
    Posted: 06-20-2019, 4:01 AM

    Hi Omer

    CommServe Instance (will be separate/unique), the two Node in the Cluster will have two Pseudo Clients to represent them. 

    In relation to your second question, for (B) & (C) here is the details.

    • B. Network Name of SQL Server (Cluster Name)
    • C. Requires SQL Server Host Name.
    Regards
     
    Winston 
The content of the forums, threads and posts reflects the thoughts and opinions of each author, and does not represent the thoughts, opinions, plans or strategies of Commvault Systems, Inc. ("Commvault") and Commvault undertakes no obligation to update, correct or modify any statements made in this forum. Any and all third party links, statements, comments, or feedback posted to, or otherwise provided by this forum, thread or post are not affiliated with, nor endorsed by, Commvault.
Commvault, Commvault and logo, the “CV” logo, Commvault Systems, Solving Forward, SIM, Singular Information Management, Simpana, Commvault Galaxy, Unified Data Management, QiNetix, Quick Recovery, QR, CommNet, GridStor, Vault Tracker, InnerVault, QuickSnap, QSnap, Recovery Director, CommServe, CommCell, SnapProtect, ROMS, and CommValue, are trademarks or registered trademarks of Commvault Systems, Inc. All other third party brands, products, service names, trademarks, or registered service marks are the property of and used to identify the products or services of their respective owners. All specifications are subject to change without notice.
Close
Copyright © 2019 Commvault | All Rights Reserved. | Legal | Privacy Policy