Commserve Migration

Last post 08-27-2014, 6:05 AM by Ali. 4 replies.
Sort Posts: Previous Next
  • Commserve Migration
    Posted: 08-19-2014, 5:30 AM

    We are planning to migrate our existing commserver to another hardware at new location. The server has been built with the same configuration and same hardware. New IP's will be assigned to the new commserve. On the basis of the documentaion we have planned the migration activity as below:

    Step 1) Disable all activities on existing Commserve

    Step 2) Kill or suspend all current backup.But question is, should we kill the jobs or suspend all jobs?

    Step 3) Initiate a DR backup on existing commserve. The location of the DR backup is another server on network.Once the DR backup is complete we will copy the DR backup file to new commserve.

    Step 4) Install new commserve on new hardware. SQL database intallation will be done earlier. (do we require to shut down the old commserve even before installing the new commserve.)

    Step 5) Install latest service pack on new commserve similar to on which we are currentely running on old commserve.

    Step 6) Since we are having new IP's, therefore we require to have new license key from commvault. We will ask commvault to generate new commserve licence key. Now the question is once the new licence key is generated, the old commserve will stop working? What is the ideal time to remove old commserve from network in terms of step numbers.

    Step 7) Register the new licence key.

    Step 8) Run the DR restore job using the DR recovery tool.


     Does it require any other steps or do we need to perform any step before or after any other step.? Please answer my queries steps wise.

  • Re: Commserve Migration
    Posted: 08-19-2014, 4:28 PM

    Basically the steps are correct, the ideal that has no job currently running.

    If you make this process with some job running, you can display error and you have to seal the base of DDB.

    When no jobs are running, run the DR.

    You also have to update clients with the new server information (IP or hostname) CommServe.

    When climbing the DR on the new server and activating with the new license, you will not use the old server and can disable it.

    But the steps described by you are correct.

    Hugs.

  • Re: Commserve Migration
    Posted: 08-20-2014, 5:41 PM

    Answers -

     

    Step # 2 - Let all job complete or kill them.

    Step # 4 – Follow the link http://documentation.commvault.com/commvault/v10/article?p=deployment/upgrade/hardware_refresh_upgrd_overview.htm for your migration.

    -          You do not have to shut down production Commserv when installing new CS. But do that before you do DR Restore and start services on new Commserv.

    Step # 6 – Old Commserv must be shut down before starting the new CS.  Apply the license key after you start the new CS.

     

    Follow the document to see exact steps.

  • Re: Commserve Migration
    Posted: 08-24-2014, 8:47 AM

    Hi Dhaval,

     

    Thanks for your suggestion.

    But i have few more doubts:

    1) What does database upgradation mean? this will be done during DR restore or do we need to perform some other steps for this.

     

    2) We are planning this for simpana 9 from cluster environment to cluster environment. Any chnage need to be done or any steps need to be performed for this.

  • Re: Commserve Migration
    Posted: 08-27-2014, 6:05 AM
    • Ali is not online. Last active: 07-03-2019, 12:32 PM Ali
    • Top 10 Contributor
    • Joined on 08-05-2010

    Hi Karam, don't think there's anything such as "upgradation" may be a typo somewhere.

    Also what type of a Cluster exactly are you configuring?  Here are some steps to setup the SQL clustering for install.

    http://documentation.commvault.com/commvault/release_9_0_0/books_online_1/english_us/deployment/install/misc/preinstall_sql_cluster.htm

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