Ask and answer questions about your self-managed and on-prem software
Recently active
Hello, EveryoneI have this log i pulled from CVPerfMgr. I will like to get analysis on the log to get where the bottleneck is, and also advice on what should be done to improve the performance.Â
Hello,I have a Commvault backup server CommServe version 11.20.0. I have downloaded a month ago latest maintenane release but not start install this.At the moment I have a problem with low disk space on Commserve and I plan to setup Remote SoftwareCache to another server ...I would like to know if this is a good procedure https://documentation.commvault.com/11.23/expert/2728_setting_up_remote_cache_on_client_computer.htmlAfter that i thought to run the download of the last current maintenance release and install it.Just one question, First I install the update on Commserve?Is this procedure correct  Should I run Update Software or Upgrade Software?Then I install update on media agents and clients…Should I run this:Thank you!Best regards,Elizabeta
Hi Team,While collecting logs, I want to upload it directly to Commvault over HTTPS. Which port is used for this, can we use a proxy? Where can I set it? Â
If we change the retention in storage policy. Will it effect old jobs or not...Â
Hi  How do I check on the Commserve, if the features below are in use? Is it in the licensing ...where would I look. I don’t think we are, but would like to check for my own benefit. Microsoft SQL Server agent - Database archiving, data masking, and table level restore
Can you please help us with getting some clarification on the CVE-2021-44228. Looks like CVE-2021-44228 also impacts the Log4j 1.x Since we still have /opt/commvault/Base64/DbJars/log4j-1.2.16.jar, we are being told by our Cyber team that according to CVE-2021-44228 on the  https://logging.apache.org/log4j/2.x/security.html Below is the snippet from logging.apache.org link aboveLog4j 1.x mitigationLog4j 1.x does not have Lookups so the risk is lower. Applications using Log4j 1.x are only vulnerable to this attack when they use JNDI in their configuration. A separate CVE (CVE-2021-4104) has been filed for this vulnerability. To mitigate: Audit your logging configuration to ensure it has no JMSAppender configured. Log4j 1.x configurations without JMSAppender are not impacted by this vulnerability. Does commvault use JNDI with Log4j 1.x ?
how  can i enable commserve livesync in commvault V 11
Hi Team, We need small update on 1 of the client which is having Cloud apps with Cosmo DB installed, so do we need apply hotfix on that server as well as we can see from CV console we cannot apply hotfix on cloud apps server, is there any way from Command Center to apply the hotfix on that server.
how to check current log4j version in commcell server?
one of our departments is saying our servers we use for Commvault are using log4shell v1.2x. They need to update it to v2.16.0.  Im green when it comes to this topic. is this log4shell a third party app which the server has installed prior to Commvault software, or is this something that Commvault installs, and is resolved by updating the Commvault software? Thats where the confusion comes into play for me, because it comes down to whether or not the department that brought this up is asking us for permissions to update it, or if this is something to do with commvault software which my team needs to handle?
