HANA 1.0 single container to 2.0 multi container upgrade

Last post 08-27-2019, 5:58 PM by Sunil Telagamsetti. 2 replies.
Sort Posts: Previous Next
  • HANA 1.0 single container to 2.0 multi container upgrade
    Posted: 08-27-2019, 4:38 PM

    After updating from a HANA 1.0 single container to a 2.0 multi container I'm unable to get the pseudo  client to discover the new databases of update the HANA information. I'm afraid that if I delete it and add it back, I will lose access to the backups that were previously created. I tried right clicking on the various parts of the pseudo client, but I see no action to discover databases. I also looked in the documentation with no luck finding info on what to do. I included screen shots of what it looks like and what it should look like.



    CV 11 SP14

    Attachment: Document.zip
  • Re: HANA 1.0 single container to 2.0 multi container upgrade
    Posted: 08-27-2019, 5:05 PM
    • efg is not online. Last active: 06-25-2020, 8:14 PM efg
    • Top 10 Contributor
    • Joined on 02-02-2010
    • CommVault Tinton Falls NJ
    • Master
    • Points 1,730

    Hi Bryan,

    You should be able to discover and refresh from the GUI for it to update, but I just heard that there is an issue with with HANA 2 SPS04.  This is currently still being looked at.  Let us know if you are running SPS04 if not then this should work.  After running the "Discover Databases" make sure you do a full refresh on the client view in the browser.

    If you are running SPS04 let us know.  I'll see if I can get some additional details.

    Ernst F. Graeler
    Senior Engineer III
  • Re: HANA 1.0 single container to 2.0 multi container upgrade
    Posted: 08-27-2019, 5:58 PM

    Hi Bryan,

    Do you see the HANA version updated in the Instance properties dialog to HANA 2? 

    Do not delete any entities, you will lose your backups.


    Can you open the instance properties dialog and click OK just to trigger a refresh in the backend?


    You will see Discover databases option at the instance level once the instance properties are refreshed.




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.
Copyright © 2020 Commvault | All Rights Reserved. | Legal | Privacy Policy