CommServe StandBy Host (DR)

Last post 06-19-2019, 12:17 PM by pereirath. 2 replies.
Sort Posts: Previous Next
  • CommServe StandBy Host (DR)
    Posted: 06-13-2019, 3:03 PM

    While deploying a StandBy host on a existing CommServe environment one of the very first steps are to install Failover package on the production host, few questions came up during the initial setup.

    1- After selecting the "Install CommServe Failover" next window brings up a path named (C:\Program Files\Commvault\ContentStore2) that is NOT in the Docs. Is this the standard behavior? 

    http://documentation.commvault.com/commvault/v11_sp15/article?p=105056.htm

    2- Step number 6 on the link above doesnt show to me during the setup, instead it automatically jump to the step 7. Should I be concerned?

    3- During the step 9, is this referencing the name of the DR Server that is going to be used?

  • Re: CommServe StandBy Host (DR)
    Posted: 06-13-2019, 9:14 PM

    When installing the Failover Package on the Production Host.

    1- After selecting the "Install CommServe Failover" next window brings up a path named (C:\Program Files\Commvault\ContentStore2) that is NOT in the Docs. Is this the standard behavior? 

    Yes. This is correct.  The CommServe Failover is installed as Instance002.

    2. No, but to be on the safe side download the sp15 media kit at the same hotfix pack level as Instance001.

    3. Instance002 is going to be registered on the CommServe Instance001.  The Instance002 "client name" needs to be a unique client name, e.g. if your production CommServe is named PRODCV, name something like "PRODCV_failover".

    ..

    As for when it comes to installing the Standby Package, you may want to raise a support call if you get stuck with the instructions https://documentation.commvault.com/commvault/v11_sp15/article?p=102847.htm.  I have seen that Step 6 where the documentation states that you can install the failover package at the same time as the CommServe has resulted in the CommServe package not being installed on the Standby.  The way around I have found around it is to install Standby Instance001 CommServe, and then install Instance002 Failover (registering onto the Prod Instance001) separately.

    Also, I would recommend that if you find documetation that you feel is incorrect - there is an email feature for each page included. :)

  • Re: CommServe StandBy Host (DR)
    Posted: 06-19-2019, 12:17 PM

    Same happened to me, CommServe Package missing on the Standby host, CommServe FailOver and SQL Package missing on the production host.

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