Applying patches/updates to Commcell server

Last post 11-02-2010, 11:08 AM by Liam. 9 replies.
Sort Posts: Previous Next
  • Applying patches/updates to Commcell server
    Posted: 07-09-2010, 2:21 AM

    What are the best practises for applying patches/updates to the Commcell server. I have mastered the install updates for all the clients through the browser but can you apply updates to the Commcell server through this way or should you login to the server and apply these locally ..?

  • Re: Applying patches/updates to Commcell server
    Posted: 07-09-2010, 8:45 AM
    • efg is not online. Last active: 09-13-2019, 10:59 AM efg
    • Top 10 Contributor
    • Joined on 02-02-2010
    • CommVault Tinton Falls NJ
    • Master
    • Points 1,678

    Its pretty much your choice.  If you have the patches loaded into the cache, you can use the "install updates" feature directly through the GUI--just select the commserver from the list of clients to update.  Or if you prefer you can install then locally as well.  (I typically use the GUI as it make the process much easier--especially for loose patches)


    Ernst F. Graeler
    Senior Engineer III
    Development
  • Re: Applying patches/updates to Commcell server
    Posted: 07-09-2010, 2:09 PM

    Hi Colin Soan,

    Best Practice for installing updates is as follows:

    Run the Download updates from the CommServe.  Once completed then, 

    Also you should get in habit of checking Maintenance Advantage site as there are many updates published here that are not part of the (Critical) level patches that are posted for Download Updates.  These patches may be needed for a specific configuration that applies to your environment.

    Download these and use the CopyToCache utility to get these patches posted to your CS CVUpdates Cache on the CommServe.  This will allow you to deploy them to all of the CommCell Components as needed.

    run a manual DR backup to 50% this will create the local copy of the DB for Protection.

    Once this is done then push updates to the CommServe only first and make sure they all apply from the version tab of the properties of the CommServe.  You can also check the "UpdateInfo.log" file and confirm the last entries state Exit code of zero

    Successfully installed updates
    ########################
    ## InstallUpdates.exe EXITING (0) ##
    ########################

    Once this is completed then update all of your MediaAgents as the CommCell may not function properly with CS and MA's on different patch levels.

    Once this is done then plan your update deployments to all of the Clients.  B.P. here is to test one of each type and confirm all goes well then plan the rollout in sections so you can run test backups to confirm all is working properly.

    Once this is done then monitor until next Full cycle completes with no issues.  This will provide you with peace of mind and good practices to follow on a regular basis.

     

  • Re: Applying patches/updates to Commcell server
    Posted: 10-28-2010, 6:05 PM

    Here is my issue, which I hope someone has a clever way around.

    What happens if we download 5 updates using the download updates function to the CommServe. We then test these 5 (in our LAB or otherwise) and find one or more to cause issues. How do we then push out only the good updates and exclude the one that causes issues, or remove it from the cache all together? 

    Is it as simple as just delete the folder related to the update?

    Our process at the moment is to use the automatic download then use copytocache to bring the updates in to our LAB environment where they are tested. Once this has happened we then push out the updates to production. Thankfully so far, none of the updates have caused any issues but there is always that risk.

     

    Your advice is appreciated.

     

    Brad

  • Re: Applying patches/updates to Commcell server
    Posted: 10-28-2010, 6:44 PM

    Hello,

    You can go to the Update Cache directory i.e. CVUpdates and rename it to something such as oldCVUpdates.  Once that is done, run DownloadUpdates via the GUI so that the CVUpdates directory is rebuilt with the latest Service Pack and critical updates.  Once that is complete, you can run CopytoCache.exe in the Base directory on the remaining updates (with the exception of the update that may have caused an issue in your lab environment).

     

    JW

  • Re: Applying patches/updates to Commcell server
    Posted: 10-29-2010, 3:39 PM

    Pushing updates using the CommCell to your CommServ server will cause the services to temporarily go down.  It should kick you off of the CommCell console.  It doesn't look like it is doing anything but if you go to your Simpana installation path ie C:\CommVault\Simpana\Updates, you can see new Updates being added.  You might want to wait a little while before attempting to reconnect to the CommCell console.

  • Re: Applying patches/updates to Commcell server
    Posted: 10-29-2010, 3:59 PM

    alternately you could monitor task manager for the services starting, once "installupdates.exe" completes

  • Re: Applying patches/updates to Commcell server
    Posted: 10-29-2010, 4:23 PM
    • Aplynx is not online. Last active: 09-18-2019, 11:53 AM Liam
    • Top 10 Contributor
    • Joined on 05-04-2010
    • New Jersey
    • Master
    • Points 1,706

    or wait until the services are back up in services.msc

  • Re: Applying patches/updates to Commcell server
    Posted: 11-02-2010, 10:08 AM

    You can also open the Commvault Service Control Manager to monitor and watch for the services to go into a "running" state.


    Thank you,
    CommVault Customer Support
    24/7 Support Hotline#: 1.877.780.3077

  • Re: Applying patches/updates to Commcell server
    Posted: 11-02-2010, 11:08 AM
    • Aplynx is not online. Last active: 09-18-2019, 11:53 AM Liam
    • Top 10 Contributor
    • Joined on 05-04-2010
    • New Jersey
    • Master
    • Points 1,706

    any commvault related programs such as SCM will close when the services initially shut down. the SCM can be opened again after its initially shut down.

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