Share Best Practices

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.