Share Best Practices

So new to Vault Tracking, and want to deploy it into our backup environment. The only concern is that in order to enable it, you have to check “Export Media After Job Finishes” The schedule is of course set to a storage policy which has up to 20 + clients associated to it. My concern is the wording of “Export Media After Job Finishes”  because its not clear if its saying it will export a tape once a job finishes as in job 1 of 20 is done it will export that tape, and so on and so forth making up to 20+ tapes, or if it is referring to the specific Job associated to it at the schedule level. For example, we have a schedule that runs for these 20+ clients that run a daily diferential backup, weekly full backup, and a monthly full backup. If i enable vault tracking on the weekly Schedule would the “Export Media After Job Finishes”  refer to the weekly full schedule as being the “job?

Our storage policies are built as follows:primary (Storeonce)sync copy 2 (storeonce)sync copy 3 (storeonce)copy 4 (tape) Although there is an option to use “validate jobs” for each of the copies, I was wondering if we could use the aux copy job report to catch any issues with the integrity of the data as running a separate validation job would be an additional overhead for the backup infrastructure. One could reduce the amount of data to be validated by defining parameters for which data qualify for validationv OR use only the tape copy for job validation as the tape drives will perform well with reading data as the data will have to be read serially (we do have combine to streams set, wonder if this will affect validating jobs as jobs could be split across multiple media) or use auxcopy reports to by pass validating jobs. Because auxcopies will read all the chunks from the source copy and write them to the target copy and make sure the indexes are also intact. So isnt auxcopies like v

Hi folks, I have a question and or rather willing to have a discussion and sharing information about how we can minimize our efforts of clicking. Possibly share scripts that we have developed and help each other out on daily tasks. We all know that Java GUI has a lot of ways to do the same and it also involves a lot of clicking.  For example, I was able to find and adapt qscripts, qoperations and API for quite a few good daily ops in my scripts, automation:Get clients associated to specific Client Group; Get Client Group to which specific server belongs; Add / Remove client from specific Client Group Start / Stop media agents maintenance mode DIP’s operations (enable/disable/remove/add) Commcell activity (Enable/Disable) Finding duplicate clients between our commcells And sure, all of it depends on the level of competence in automating, but Commvault being ‘old dinosaur’ can still be automated a bit. Now, for example I cannot find a way to write a script which switches preffered media

When the pandemic hit, we were forced to quickly adapt and answer a bunch of questions we’d never asked ourselves: how can we keep in touch with our colleagues when we’re not in the office? And how can we make sure we are still efficient while working from home?It quickly became apparent that one, seemingly small issue could prove catastrophic: our information system is designed so all business documents are located on our servers and on our work computers. But this also meant that many wouldn’t be able to access these documents from home.Since the employees were already familiar with the backup system, this new opportunity only confirmed our desire to modernize the complete system and to digitize business processes.Everyone was aware that these changes were necessary, that it would help them work through the emergency, and, most importantly, that working from home wouldn’t be an insurmountable problem.A new short manual was compiled to help employees adapt to working from home, with a

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

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.