Commvault Cloud Topics

LDAP is a supported function to manage distributed directory information services within Hedvig Storage ClusterSetting up LDAP/AD Server Action: Log into any of the Hedvig Storage Node and select the LDAP/AD Configuration from the far-right corner   You will then be presented with a LDAP/AD configuration screen, depending on whether you choose to use "Use Domain Name" or not, different fields will be populated (Note - SSL can only be used when not using "Use Domain Name") Hedvig RBAC is based on the concepts of: Tenants, which are groups of users: You can set up multiple tenants per cluster. You can set up multiple servers per tenant. Users assigned to these tenants: You can set up multiple users per tenant. Each user can belong to more than one tenant Here are the details for each of the fields: Tenant: This is a pre-configured Tenant that you would like to target an AD for. To configure/add goto User Administration / Tena

The following procedure allows you to safely update Fujitsu Appliance iRMC Password which won't impact operations such as: RHEV-M Hardware failure alerting Important Note - for the HyperScale Appliance\, Commvault leverages the IPMI protocol to monitor the physical hardware by design\, and reports back to Command Center if there is a fault. IPMI - Intelligent Platform Management Interface is a set of computer interface specifications for an autonomous computer subsystem that provides management and monitoring capabilities independently of the host system's CPU, firmware and operating system. The following procedure are applicable for the following use cases: Updating iRMC Password for security purpose Resetting iRMC Password if it is forgotten or lost IPMITool is installed at the Guest OS level (Redhat OS)Updating iRMC Password First, you will need to establish a SSH session onto the Guest OS (HyperScale RedHat 7.#) Then input the following command: # ipmitool user set password

When a Teams chat is started it automatically creates a Exchange group mailbox, an OneDrive account for that same group mailbox and a SharePoint site for that Teams chat. All conversations are put in the Exchange group mailbox and up until October 2020 they could be found under the folder Conversation History\Team Chat. Now here comes the fun part, starting October Microsoft changed something in how they save the chats and they moved the chats to a new folder named ~TeamsMessagesData.During the roll-out of a M365 customer we encountered that the teams chats were not being backupped past September 2020 and as I could not find any issue with the back-up nor any configuration issues we opened a case with Commvault to research the issue. Big was our surprise as in the first reaction from the Commvault engineer I received the answer to my question, namely a hidden additional setting which would enabled the back-up of the new Teams chat folder, being:IncludeTeamsMessagesDataLocation =  HKLM\

Issue There was a known issue identified with Redhat Gluster where the Capacity is reported incorrectly This is due to an incorrect parameter on the Gluster known as shared-brick-count which will count how many bricks share a file system and how the disk space is divided accordingly (within the Gluster) Methods: Method 1 - if you are on the following Service Pack & Hot Fix Pack SP15 & Hot Fix Pack 35 SP16 & Hot Fix Pack 27 SP17 & Hot Fix Pack 12 Method 2 - prior to the above Service Pack or Hot Fix Pack  IMPORTANT NOTE - this only needs to be done once and will be applied across the Gluster\, no further remediation is required. Method 1 Commvault introduced an additional feature under (/opt/commvault/MediaAgent) which will generate the shared-brick-count script in (/usr/lib64/glusterfs/3.12.2/filter/) for all the nodes Navigate to the following location # cd /opt/commvault/MediaAgent   Execute the following script # ./cvavahi.py fix_gluster_

Optimized For concurrent LAN backups is an option in media agent properties that helps to optimize the Operating System resources on Media Agent machine. It's recommended to enable this where there are multiple clients backing up to media agent.While enabling "Optimize for..." option is generally recommended, performance wise and when there are firewall rules in place, we need to consider the type of firewall rules in place. Generally speaking adding CVD port number (8400) as additional data port on the Media agent firewall rules is recommended for performance improvements. Additional ports are not needed on the client side here. System will only use the CVD port (default 8400) on the MA side as additional port so adding other ports on the MA won't help! Please note with CVD port in additional data ports, Client will transfer the data directly to MA on CVD port bypassing the firewall tunnel and it’s protocol.