Share Best Practices

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 

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.

Hello,I’m experiencing an issue with backups from an IBM i server using Commvault.Recently, the scheduled backup jobs finish with the status “Completed” and without errors, but when reviewing the backup contents, no data appears to have been backed up.In this case, the backup configuration is set to back up only one specific library, and this is precisely the library that is not being backed up.So far, I have verified the following:The Check Readiness test is successful on both the IBM i client and the Proxy. The IBM i user configured for Commvault has the required privileges. Backups were working correctly last week. The backups run during early morning hours, when there is no system activity. I tested the Save While Active parameter using “*LIB” and “*SYNCLIB”. No network connectivity issues have been detected.Has anyone experienced a similar situation where the backup job completes successfully but the configured library is not backed up?Any guidance or suggestions on additional che

Hi everyone,I asked Arlie about encryption handling when doing auxiliary copy (tape-out) from an encrypted HPE StoreOnce Catalyst Store https://support.hpe.com/hpesc/public/docDisplay?docId=sd00003761en_us&page=GUID-6D031310-DD0A-46AC-96E5-3B3F843EEA63.html.According to Arlie, if the tape storage policy copy is set to "Preserve encryption mode as in source" (the default), the encrypted backup data from StoreOnce should remain encrypted when written to tape—no decryption/re-encryption needed.However, I'm opening this thread for real-world confirmation from folks running this in production. Does the encryption truly persist end-to-end from StoreOnce to tape in a real scenario? For the HPE MSL G3 tape library (which supports hardware encryption via encryption stick), is the StoreOnce software encryption sufficient on its own, or are there best practices requiring the hardware encryption stick to be enabled?Looking for experiences and best practices on whether the StoreOnce encryption

Hey community,We just upgraded Commvault from 11.36 to 11.40 and immediately hit OCI Oracle database backup issues. Jobs failing that worked perfectly before, now troubleshooting agent configs and Oracle parameters settings (Case 260207-250). With this occasion, let's get real about rollback scenarios. Official line is no direct rollback exists after a platform upgrade completes. But is it legit to use a pre-upgrade CommServe DR backup to restore the CommServe to 11.36, then manually rollback the MediaAgents and clients to match?Does this actually work in practice? Has anyone pulled this off successfully?Please for your feedback,Nikos

Hello communityI am having an issue with getting the compliance lock unlocked on all secondary copies of my storage policies.  i have completed the following Filled in the form under resources on the website to get compliance lock lifted, using Commcell ID, Primary Copy name and ID, secondary copy name and ID and also passphrase which is correct. killed all logins using Qlogout.exe -all Logged back in using an account in the Masters Group ran the following the xml file provided by Commvault only has the IDs for the primary copy and the secondary copy.  It has no mention at all of the names of both the primary and the secondary  

Hi,The maximum certificate lifetime is going down:From today until March 15, 2026, the maximum lifetime for a TLS certificate is 398 days. As of March 15, 2026, the maximum lifetime for a TLS certificate will be 200 days. As of March 15, 2027, the maximum lifetime for a TLS certificate will be 100 days. As of March 15, 2029, the maximum lifetime for a TLS certificate will be 47 days.Certificates for the Command Center (Tomcat web server) must be manually renewed and updated.Does CV have a recommended procedure to tackle this in future or should everyone find their own solution?/Piippu

Hello Fello Commvaulters I hav the task of moving our current Index Cache and DDB database dat from their current drives I & D respectively to two new drives on the SAME media agent?  I can see a workflow which Ive used many times to move the data between the old media agent and the new one.  This is movement from within the same box. I dont see a WF in how to do this.  Anyone any ideas?  Also worth pointing out the “Index Server” tab on my media agent is greyed out.  

Hello Team,How can we enable Journaling on o365?Note: On on -prem it was enabled but it will be decommissioned soon as we moved to Exch Online.

what we keep the directory space if we want to install commvault commserve in redhat linux 

For Oracle database backups on Commvault, what is the recommended approach to use retention rules? The recommended approach is to use retention rules based on number of cycles or days? 

Good morning, We are new to postgres databases and are implementing our first production cluster soon.  What are you all using for your log backups in terms of scheduling?  We are running in continuous archive mode and currently have backups every 15 minutes.  Even 2G  backups are taking under a minute. What are the considerations for setting this? If our RPO is 5 minutes, would it make sense to backup every 5 minutes, or is that trying to fit Commvault into a high availability box that it is not designed for?If using FSBasedBackups, are you also using regularly scheduled dump based backups?  In what scenario? Thank you very much, this forum has been fantastic!-Chris