Linux media agent debug level

Last post 04-25-2013, 9:47 AM by efg. 5 replies.
Sort Posts: Previous Next
  • Linux media agent debug level
    Posted: 04-25-2013, 3:58 AM

    Hi,

    I have to increase the debug level of auxcopy on a linux media agent. In Windows I find the SetLogParamsGui.exe. Is there something to configure the debug level on Linux?

     

    Thanks.

  • Re: Linux media agent debug level
    Posted: 04-25-2013, 8:36 AM
    • efg is not online. Last active: 10-22-2019, 2:17 PM efg
    • Top 10 Contributor
    • Joined on 02-02-2010
    • CommVault Tinton Falls NJ
    • Master
    • Points 1,678

    There is no such utility on the Unix/Linux clients, but then it is not needed since the key can be set via the CommCell Console. 

    Right click on the mediaagent in the commcell console, and select properties:

    Then go to the "Registry Key Settings" tab and click Add.  From there add the debug registry key that you need to set.  Here is an example for increasing the debug for the AuxCopy.log:

    After setting the appropriate value, select OK, and the registry key will be set on the Linux MediaAgent:

    If you are not sure of how to set this key or what the key value should be set to, please contact support, and any engineer should be able to assist you.

     


    Ernst F. Graeler
    Senior Engineer III
    Development
  • Re: Linux media agent debug level
    Posted: 04-25-2013, 8:40 AM

    Hi,

    Thank you very much. Is this information from Books Online?

  • Re: Linux media agent debug level
    Posted: 04-25-2013, 9:08 AM
    • efg is not online. Last active: 10-22-2019, 2:17 PM efg
    • Top 10 Contributor
    • Joined on 02-02-2010
    • CommVault Tinton Falls NJ
    • Master
    • Points 1,678
  • Re: Linux media agent debug level
    Posted: 04-25-2013, 9:20 AM

    I didn't find this regkey in Books Online. Maybe it is an undocumented key? Or for internal use only?

    Thanks.

  • Re: Linux media agent debug level
    Posted: 04-25-2013, 9:47 AM
    • efg is not online. Last active: 10-22-2019, 2:17 PM efg
    • Top 10 Contributor
    • Joined on 02-02-2010
    • CommVault Tinton Falls NJ
    • Master
    • Points 1,678

    Debug Keys are typically for internal use only since enabling them does substantially increase the logging as well as can negatively impact performance of the iDAs.  Care should be taken whenever adding/enabling these keys, and typically should not be done without support assistance.  I believe it is for this reason that these keys are not be included in BOL.


    Ernst F. Graeler
    Senior Engineer III
    Development
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