Using DB2 TSAMP with Commvault

Last post 10-23-2019, 12:29 PM by jfischer. 0 replies.
Sort Posts: Previous Next
  • Using DB2 TSAMP with Commvault
    Posted: 10-23-2019, 12:29 PM

    We are using TSAMP for our DB2 HADR set-up on Linux.  This doesn't work great with Commvault since it requires us to manually do a force sync in the client GUI to get the active nodes to switch when we do a failover.

    After chatting with support it seems we can use this kind of command:

    cvclusternotify -inst InstanceName -cn ClientName [-start | -shutdown]

    somewhere in our TSAMP configuration to have the node update automatically.  Our DBA's are very hesitant to change the built-in scripts (can't argue that) but has anyone done this successfully?  Or is there another way we can accomplish the same task?


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