Share Best Practices

Hi!As Server 2016 will go out of support anyways within the next year, I consider proceeding the upgrade before, as 2019+ support larger cluster sizes than 64 kb which should drastrically improve file system defragmentation and by that HDD performance.The “wasted” should be less of a deal, as Commvault saves data in big chunks of 1+ GB anyways. I assume that Commvault does not have trouble with the cluster size (the storage part in documentation is generally pretty “thin” regarding file systems, best practices etc.).Sidenode: You should definitely add, that partitions/drives above 64 (actually more 63.5) TiB can’t be snapshotted with VSS, nor can chkdsk do anything on those. But the main question: Is there any problems to in-place upgrade Windows Server 2016 to 2025?It would be big pain to migrate all that data (we have one machine running all services/functions) to a new (pricy!) server as long as the hardware is still supported/maintained. I’ve read and old thread that recommended do

We have a large MongoDB Production sharded cluster of approximately 70–80 TB, consisting of around 120 nodes running Rocky Linux 8.10. Could you please check  and confirm whether Commvault supports backup and recovery for a MongoDB cluster of this scale? We would also appreciate any information on known scalability limitations or recommended sizing guidelines.Also , whether normal Mongo Snap Backup or Percona would be useful in this case ? 

We are planning to implement Commvault with HPE StoreOnce 3660 NAS share, please advise the best Practice for the configuration level. - Is it will enable Deduplication & Compression in hardware level and disable these features in Commvault end. - Is it will run backup of synthetic full (or) full + Incremental.Please share best practice document to implement this solution. 

Oracle RMAN backup data buffer write failure error

We migrated all data to a media agent in the cloud. The Commserve is still local in our company. We would like to install the Commserve on our media agent in the cloud. (Data is only ussed for Archive, backup is moved to cloud)I tried to install the software on the media agent, but you cannot select the option to install the Commserve software. I must uninstall the media agent software and then install the Commserve and media agent software. We are running 11.32.XX (no production only archive)Is there a best practice to do this? Is there any documentation?Thanks in advance!

Hello All,I need some clarification regarding Storage Policy retention configurations for DB2, and Oracle command-line backups initiated through DB2 and RMAN commands. Version - 11.40My understanding is that Commvault currently manages command-line log backups based only on days-based retention and not cycle-based retention. By Cycle, I am referring to the complete database backup chain consisting of Full + Incremental/Differential + Log backups as part of a cycle.My first question is whether the cycle retention condition is applicable to Incremental/Differential/Delta backups initiated through the command line. It appears that it may be, but the behavior is not entirely clear.In the case of Oracle, the situation is even less clear because archive log backups are also classified as Incremental backups. As a result, it is difficult to determine whether these log backups follow cycle-based retention or are retained solely according to the days-based retention settings.If command-line dat

We’re currently planning to migrate our DR Commserve from On-prem to Azure Cloud as part of Hardware Refresh project.Current environment -Primary CommServe (Production) hosted in a On-prem data center A. DR CommServe configured and running in On-prem DC B. Backups are getting backed up locally and connected with Production Backup Server A. Currently everything is running on physical backup environment (Media Server, Storage, Primary and DR Backup Server) Live Sync backups are configured in every 1 hour between Primary and DR Backup Server.Planned Changes - Onprem DR Backup Server needs to decommission, and it needs to migrate in Azure cloud. Primary Backup server will run as is in Onprem DC A. Post successful migration, Primary Backup Server will be on physical environment and DR Backup server will run in Azure cloud. Hostname will be same of DR backup server in Azure cloud. Only IP will be change. No changes for Primary backup server.Questions / Clarifications Required -Best practices

Hi Team,We are using the DAG database for Exchange backups. We are currently trying to restore PST files for some users from the DAG Full Backup.The Create Recovery Point job completed successfully. However, when we open the available recovery point from the List Recovery Points section, we are unable to browse and view the users/mailboxes for recovery.We have also verified the required prerequisites on the selected MediaAgent, including the Commvault Exchange package and Microsoft Outlook 2013 64-bit, which are installed on the MediaAgent.Additionally, we attempted the PST restore, but the restore job remains in Running state without any progress/update for more than 30 minutes. The logs indicate repeated messages related to the process not receiving network messages.We have attached the relevant screenshots and logs for your reference.Could you please review the issue and advise why the users/mailboxes are not appearing when browsing the recovery point and what steps are required to

Hi all,After installing the MediaAgent Package on some Windows Servers (These just require the component and do not not act as a Data Mover or host a DR Share) I get the once a day 64:1142 Critical Code Event logged:  Administrative share are enabled on the MediaAgent XXX which could lead to potential security exploits, please review and take necessary steps.Having reviewed https://kb.commvault.com/article/72274 this article only really seems concerned with disk libraries and DR Shares that use an Admin share in its path. I have 2 servers that this is being logged in event viewer for, yet they only have the default C$, Admin$ and IPC$.  Should Commvault be flagging the C$ as something that should be removed?  Indeed if I apply a reg key (AutoShareServer = 0) the alert is suppressed, but this also removes the Admin$ Share.   Are these alerts in the Event Viewer supposed to be triggered for these default Shares by design or is it being over zealous and picking up these in error?  The Cri

We use VMWARE and use lots of SQL AGS.  We backup the SQL databases at the AG level however I am wondering what would be the best way to recover incase of a cyber event.   The plan I have is to take an initial snapshot all the VMs after installing SQL server on a VM and then use SQL and MSDB databases backups; and every time a server is patched take a full file system backup of the OS and location where system databases are stored.  SQL Agent would continue to protect the user databases  When a system fails completely > Restore from initial VM level backup  >  Restore file and folders via the agent based backups > Restore the databases via the DB backups Any other ideas...  SQL team dont want vms to be snapped regularly 

We are using a standalone tape drive with a 3-tape rotation.Our current plan is: We have 3 tapes. Every Friday at 9:00 PM, we perform a full backup. On the remaining days, we perform incremental backups at 9:00 PM. Every Friday at 7:00 PM, the operator changes the tape, and the new tape is used for the full backup at 9:00 PM. Week 1 uses Tape 1, Week 2 uses Tape 2, Week 3 uses Tape 3, and Week 4 uses Tape 1 again. After Week 4, Tape 1 is ejected at 7:00 PM on Friday and sent to HQ for long-term storage. HQ then sends us another tape, which we label as Tape 1, so we always continue with a 3-tape rotation. I have a few questions about how Commvault handles tape retention and exports: Does the retention period matter for tapes? For example, if my storage policy has a 14-day retention, what happens when I insert a tape again after 14 days? Will Commvault automatically move it to the Scratch Pool and overwrite it, or can I still browse and restore the data that is physically on th

Hi, We’re looking for designing a commvault solution using companies. We would like one company per company that support, and then one company connected to this parent company using the reseller mode for different solutions we are working on with this subcompany. Is this the intended design choice for this type of environment?I’m also having a bit of trouble with understanding the access control to users in multiple companies. How can we control this? At what level should I be creating a user (commcell, parent company, subcompany)? And how do I delegate a user multiple subcompany access or full company access? It seems like I can not give company access to a commcell user. That would mean that I would need to create one subcompany login and role for each subcompany that we create, is that really by design?I can’t really see the vision here in commvaults access control strategy, and can’t seem to find any documentation specific on companies either. Kind regards,Daniel

Hi team,We recently encountered an issue while restoring files from a VM backup to the original server's C: drive during a major application outage.The affected server is an application server that lost critical files required for the application to function. To recover the application, we initiated a file-level restore from the VM backup. However, the restore to the original server took significantly longer than expected (approximately 9 hours), which impacted the overall recovery time.As a workaround, we restored the required files to the Backup Media Agent and then manually transferred them to the affected VM. This approach allowed us to recover the application sooner than waiting for the direct restore to complete.To help us improve our recovery process, could you please recommend the best approach to mitigate similar situations in the future? Specifically, we would like guidance on the following:Best practices for performing file-level restores from VM backups during critical inci

HI,we would like to upgrade our commvault PF from v11.28 to v11.40,I would like to know if someone did it lastely and how you did it please if you have a detailed procedure please share it with me it would be very helpful :)thanks

We are currently using Configuration policies for Exchange online. It ignores the Retention time of the storage policy. I want to start using the retention settings of the Storage policy again.   Is there a reason that you would use Configuration Policies for Exchange? Can you not just use te retention time of a plan or storage policy? 

Commvault is incredibly powerful.But that power comes with complexity—and complexity is where mistakes creep in.I’ve worked in enough environments to see the same patterns repeat:Backups are “working”… until they aren’t Performance slowly degrades Restores become harder than they should beAnd most of the time, it’s not a product issue.It’s configuration.Here are 10 Commvault configuration mistakes I see all the time—and how to avoid them. 1. Building Everything Around a Single MediaAgentIt works at first.One MediaAgent. One place for everything. Simple.Until:Jobs stack up Throughput drops That one system becomes your bottleneckFix:Start with at least two MediaAgents and distribute workloads.If everything depends on one MediaAgent, you don’t have resilience—you have risk. 2. Undersizing the CommServeThe CommServe is the brain of your environment.And yet, it’s often treated like an afterthought.What happens:Slow job scheduling UI lag Reporting delaysFix:Proper CPU/RAM sizing Fast storage

Hi everyone,I'm working on a custom set of permissions for our MSSQL admins to allow them to perform on-demand backups. Despite granting what I believe to be more than sufficient privileges, they are still encountering errors.The process works perfectly when the user has master rights.Current permissions: Error with those: Has anyone successfully configured a least-privilege role for this scenario and could share?

Description:We are currently planning a transition of our Commvault environment and need guidance and best practices for our scenario.Current Setup:Primary CommServe (Production) hosted in a colo  data center LiveSync DR CommServe already configured and running in Azure (Cloud) Media Agents and backups are currently aligned with the colo-based production CommServePlanned Change:The colo site is being decommissioned All workloads and servers are being migrated to Azure The existing DR CommServe in Azure will be promoted to Production Post transition, backups will be fully aligned to Azure workloads and infrastructureObjective:We want to:Promote the Azure DR CommServe to act as the new Production CommServe Reconfigure clients, Media Agents, and storage policies to align with Azure Safely decommission the existing colo-based CommServeKey Questions / Clarifications Required:LiveSync Failover: What is the recommended approach to promote DR CommServe to active Production? Client Connectivity

In a lab setting, I've installed several Commvault servers for various use cases, including customer demos. Below is my take on designing a Commvault environment. It’s easy to build a Commvault environment that works.It’s much harder to build one that still works a year later, under more load, more data, and more expectations.Because scale doesn’t break things immediately—it exposes the shortcuts you took early on.I’ve seen environments that looked perfectly fine at deployment:Backups running Jobs completing Storage holding upThen growth hits.More VMs.More data.More retention.And suddenly:Jobs start missing windows Deduplication performance drops MediaAgents get overloaded Restore times creep upThat’s not a failure of Commvault.That’s a design problem.Let’s talk about how to build it right from the start. 1. Start with Architecture, Not JobsOne of the most common mistakes is jumping straight into creating backup jobs.But jobs don’t define your environment—architecture does.Core compone

Hello,One of our clients has an On-prem CommCell with IBM 3576-MTL6 library with 6 drives and over a thousands tapes. Considering customer is planning workloads/clients migration to a new CommCell is it possible to migrate indexes of these tapes and lift and shift actual tapes, however without migrating the actual library and tape drive hardware. What is the best option? Thanks Tomas 

A design consideration for Azure workloads spread across three Azure regions (A, B, C). Additionally, we have a Media agent (bare-metal server with disk storage for primary backups) that we want to host in Azure in one of these regions (A/B/C). Our CommServer is hosted on-premises.looking for advice on the best deployment strategy for access nodes / proxy servers:    1. Should we deploy separate access/proxy nodes for each workload in every region?    2. Can we combine access nodes / proxy servers for multiple workloads? If yes, what would be the best possible combinations?The workloads include:    • MySQL Flexible Servers    • PostgreSQL Flexible Servers    • SQL Managed Instances    • SQL Databases    • Storage Accounts (File & Blob)    • Virtual Machines    • VM Scale SetsGoal: compatible with multi-region expansion, Optimize latency, cost, and operational efficiency while ensuring secure and reliable access to each workload.Any insights, architectural patterns, or references to

The name and description suggest that the output will display all index servers and their associated clients.My tests have shown that index servers are visible to Solr clients, but not to "regular" clients (v1 or v2).I expected to see all active "non-Solr index servers" listed under "Active Standalone Clients"This group always shows up as empty for me.What am I doing wrong?

Hello,Commvault 11.32.x is running on a Windows 2019 server.We noticed that when we need to shutdown or reboot our CommServe in case of Windows Updates for example, the whole process takes at least 10 minutes, more often 15 to 20 minutes… One could understand that it is difficult to afford with such amount of time for each reboots.The shutdown process stays “ stuck “ for several minutes on the step : “ Shutting down of service: Group Policy client “.   A case has been opened at Microsoft support, investigations pointed out that this huge amount of time needed is due to the execution of Commvault D:\Commvault\ContentStore\Base\StopProc.vbs.If I am not wrong, this file is supposed to allow current jobs enough time to complete smoothly.MS support asked if it would be possible to “ disable “ temporarily the execution of this file, in order to test if that solves the issue.-→ Does somebody else is facing the same Commvault behavior at shutdown ?-→ Knowing that each time we shutdown/reboot C

I’ve noticed that when installing the File and MSSQL agent on a client, it populates the networking quicker if you add the default file subclient to a storage policy before adding the sql subclients in.