Commvault Cloud Topics

Hello All;I found this topis: An I have similar problem in with Data Domain, in the logs I found taht StorageAcceleratorAutoDisabledUntiland i have a question:Where I can found exactly this keys on Linux and Windows systems? MediaAgent/StorageAcceleratorAutoDisabledUntilMediaAgent/StorageAcceleratorConsecutiveFailureCount I have installed on clients Media Agent and client can communicate with DD.

   We are in the unfortunate process of migrating from VMware to Hyper-V.   We are in mid migration and I am finding that the snapshots are taking longer and longer.   Normally snaps are about 15 to 30 min.   Now they are taking over 5 hours for a quiesced  snapshot.  After the snapshot is done, the Backup Copy runs quickly.   During the Snapshot job, I see lots of log messages about CHyperVInfo2::RunParallelVMSnapshotTask() - No available thread found for creating software snapshot of virtual machine XXXXXXXX.   I can not find any setting for the number of threads that Commvault will use to talk to Hyper-V.   I have had a support call open for a bit but not felling like it is making any progress.   This feels like it should be a 101 type question.    Does anyone else have delays with their Hyper-V snapshots?

Hello Commvault Team,We are designing a Commvault backup architecture for an OpenShift GPU environment and would like to confirm the supported network architecture.Our environment has the following network connectivity: The CommServe and MediaAgent can communicate with the Access Node. The Access Node can communicate with the CommServe/MediaAgent, OpenShift API Server, and OpenShift Worker Nodes. The OpenShift Worker Nodes cannot directly communicate with the CommServe or MediaAgent. The Worker Nodes are connected only to the OpenShift Service Network and do not have connectivity to the Backup Network. The Access Node has connectivity to both the OpenShift Service Network and the Backup Network. We are considering using the Commvault Command Center Network Topology feature to control the backup communication path.Our desired backup data flow is:OpenShift Worker Node / Backup Pod → Access Node → MediaAgent → Backup StorageIn this architecture, we would like to avoid requiring di

I got the following error when backup a vm:Error code: [19:2601]Description: The job is pending because all access nodes to launch the job are overloaded.Source: cms01109c1us02, Process: JobManagerI have no idea what the error mean. I run the backup gateway on my Windows to backup a remote VMware virtual machine.

Why can’t I find these on the readiverse.com site?Commvault Cloud Professional – advanced recovery and workload expertise, including Cloud Rewind or Cleanroom Recovery coursework Commvault Cloud Expert – advanced cloud engineering and resilience leadership, including Cloud Engineer coursework, advanced feature courses, Cloud Rewind, and Cleanroom Recovery 

Hello Commvault Team,We are currently using Commvault 11.44 to protect Red Hat OpenShift environments.According to the current compatibility matrix, Commvault 11.44 supports OpenShift up to version 4.21. We would like to ask if there is any roadmap or estimated timeline for supporting OpenShift 4.22.Many enterprise customers prefer to deploy and operate EUS (Extended Update Support) versions of OpenShift because of their long-term stability and extended support lifecycle. As a result, timely support for new EUS releases is very important when planning production upgrades.Could you please advise:Is OpenShift 4.22 support currently planned for Commvault 11.44 (or a future maintenance release)?If so, is there an estimated timeframe for when support will become available?Based on previous OpenShift releases, how long does it typically take after Red Hat GA for Commvault to officially certify and support a new OpenShift version?We understand that compatibility testing and validation require

I have a customer running 11.40 and Commvault now has the combo tiers for cloud storage configured by default. My question resides in which tier the bucket should be created. The customer had previously created a bucket in AWS (this may come into play later) that was used to create a Cloud Library in Commvault using the AWS Glacier Deep Archive tier. When examining the data in the bucket, we can see the CHUNK data is written to Glacier Deep Archive however, the index metadata is showing under Glacier Instant Retrieval. This seems wrong to me.I have read that Commvault will apply an Amazon storage class header to every upload API call and then writes the data to the bucket, which is part of what is allowing the CHUNK data to be written to one tier with the index metadata to another tier. I’m starting to believe that the storage class header only is being applied to the CHUNK data and the metadata is using whichever storage tier the AWS S3 bucket was created with. Documentation doesn’t m

Hello Commvault Community,I am currently working on a project where the client requires us to confirm compatibility between Commvault and Red Hat OpenShift.According to the official Commvault documentation, Release 11.44 officially supports OpenShift up to version 4.21. However, we would like to know if OpenShift version 4.22 works properly with Commvault 11.44 despite not being officially listed yet. Has anyone in the community tested or run backups/restores on OpenShift 4.22 using Commvault 11.44? If so, did you encounter any issues or limitations? Any insights, feedback, or shared experiences from your actual implementations would be greatly appreciated as we need to verify this for our customer's project requirements.Thank you!

We are running into this wired issue infra stack is vmware 7, vmware 8, 2 instances of Commvault one with vm proxies used for VMWARE 7 another one is HSX with HSX nodes for VMWARE 8.  Datastore is on pure storage.  We are in transit and evenrutally migrate to HSX  This is happening on both the environments V7 and V8 (separate cv instances) The issue we run into is that when there are open snapshots; the Intellisnap backup randomly goes into hung state; where in it gets stuck during the phase(pre hardware snapshot phase) where VMWARE snapshots are taken and deleted and never proceeds into taking the storage snapshot; as a result the next morning there are open snapshots on all the VMs for that job during production hours which I then manually cull using a powershell script.  What I don’t understand is how does manual deletion works (using a script) when Commvault support says they are getting timeout in the logs when trying to delete the snapshot and that could be the issue.    RemoveSn

Hi all,  I had a question. Could not find it with a search, so maybe someone can help me out. Does CommVault support Virtual Trusted Platform Module (vTPM)?I know Rubrik does not support it yet.  Best Regard

Hello Commvault Team,I have a question regarding the operating system support matrix in Commvault 11.46.The Linux File System Agent System Requirements document lists support for:Red Hat Enterprise Linux 10 Oracle Linux 10However, Rocky Linux 10 and AlmaLinux 10 are not listed.At the same time, the 1-Touch and Virtualize Me for Linux System Requirements document includes support for AlmaLinux 10 (and Rocky Linux 10).This seems inconsistent, so I would appreciate some clarification.Could you please help answer the following questions?Why are Rocky Linux 10 and AlmaLinux 10 supported for 1-Touch but not for the Linux File System Agent? Is this an intentional support policy or simply a documentation difference? Are Rocky Linux 10 and AlmaLinux 10 currently under validation for the Linux File System Agent? Is support planned for an upcoming Maintenance Release or LTS release?We are currently planning new Linux deployments, and understanding the roadmap will help us decide which operating s

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

below are the details regarding backup gateway which is only says windows as supporting os , is linux supported to azure backup gateway to protect azure worklloads  https://documentation.commvault.com/11.42/software/system_requirements_for_azure_backup_gateways.html?view=saas https://documentation.commvault.com/11.42/software/system_requirements_for_on_premises_backup_gateways.html?view=saasbut for media agent for saas support all the os  MediaAgent: System Requirements

Hi all,just wondering if anyone can help me. I’ve noticed on our Hyper-V hosts then when a backup is triggered in CommVault the system event log on the hosts are flooded with Disk and partmgr warnings for specific disks.I’m just wondering if this is normal behaviour or something we need to look in to? For context, these hosts are running Windows Server 2019, are MediaAgents for all our VMs and we are running CommVault version 11.36.102.The disks presented to the cluster are CSVs and are presented via iSCSI from our NetApp.I cant see that its causing any hard to the backups as they are completing successfully. The Vms and hosts also appear to be fine - but not sure what could be causing these warning or how to remediate them. 

Hi All, what is the best way to backup windows server with dfs replication via windows file agent ? 

I was teaching a CV Engineer trainingsome time ago, using a lab setup for demos that I upgraded from 11.32 to 11.40. I created a disk storage pool to demo things. When I started to configure dedupe, I only got the possibility to choose the MA for the DDB, not the location (vloume / folder), so the DDB ended on the C: drive. Is this because the upgrade went wrong, or is this by design? If it's by design, why???

Over the weekend, we started seeing errors in SharePoint online backups for all the tenants we backup with the error: “ Failed to validate any of the configured Azure Apps against the SharePoint Tenant Admin site. 1) Please verify the SharePoint Tenant Admin Url. 2) Please check the credentials and permissions for the configured apps. 3) Please ensure Custom App authentication is enabled on the SharePoint tenant.<br/>Source: xx, Process: SharePoint”From logs on the Access Node:CheckOffice365CredModern - Office365 app credentials incorrect : CheckOffice365CredModern - Error is: The remote server returned an error: (401) Unauthorized. What we have doneVerified the Azure App secrets are not expired Verified DisableCustomAppAuthentication on the tenant is set to false Verified Azure app API permissions: Microsoft Graph:  Application.ReadWrite.All, Application.ReadWrite.OwnedBy,  Directory.Read.All, Group.ReadWrite.All, Policy.Read.All, RoleManagement.ReadWrite.Directory, Sites.FullCo

Hi,I keep seeing an irritating warning during Hyper V backup. One host in the Hyper V setup has been de-configured and the SW uninstalled, and the node has been removed from the list in the Hyper V Instance. Also, it does not show up in the preview for the vmgroups. Even so, the warning (Could not establish connection host [.], results may be incomplete) appears immediately when the backup runs. How can I get rid of this host? Please assist.

Hello,We are currently running backup on Commvault (FR42) for MongoDB Atlas protection with an enterprise customer. Our understanding iis that Commvault orchestrates native Atlas cluster snapshots through the Atlas REST APIs, with no backup copy possible — the data never leaves the Atlas/AWS perimeter and cannot be materialized on a Commvault Cloud Lib...However, MongoDB Atlas natively supports exporting Cloud Backup snapshots to a customer-owned object store (S3, Azure Blob, GCS) via the Atlas Admin API, including S3 Object Lock immutability and PrivateLink transfer. Since Commvault already integrates with this API for snapshot orchestration, we would like to understand:Is there a technical or product reason why Commvault does not leverage the Atlas snapshot export API to provide a true secondary copy (backup copy / air-gapped copy) of Atlas data under Commvault management? Is such an integration on the roadmap for an upcoming Feature Release? If not, what is the recommended Commvault

Hi guys,If I want to achieve the best dedup efficiancy, I have to set the Max Open Files in the Commvault subclient(s) of an Oracle Instance to 1.Otherwise, RMAN will multiplex the number of files allowed into one channel / stream, which leads to poor dedupe ratio for the backups of this databases.Is there an option to influence the parameter of default subclient during instance creation when a new instance is discovered ?Setting the amount of streams and restricting the MaxOpenFiles might be beneficial when adding larger amount of Instances to the environment and where disk or cloud is the primary backup destination.rgdsKlaus

We have observed the following: Operating System: Red Hat Enterprise Linux 9.7 MongoDB Version: 8.0.20 mongodump Version: 100.16.0 Commvault Version: 11.42.90 iDataAgent Version: 11.42.90 We are facing an issue where incremental backups fail, while full backups complete successfully. The error indicates that oplog creation failed. However, when we perform the oplog dump manually, it completes successfully.We also observed that with Commvault/iDataAgent version 11.36.80, both full and incremental backups complete successfully. However, the restore operation fails because the MongoDB service attempts to stop but is not stopped properly by the iDataAgent.

We are planning an upgrade from 11.32 to 11.36. With the deprecation of the web console, does this mean that the legacy Compliance Search (not the CommandCenter version), will disappear? We have users still using that, and don’t see many benefits to the CommandCenter version.

Backup Server: 4.172.1.4: The value of 'allocated pages threshold' has been set to 40%. Backup Server session id is: 68. Use this value when executing the 'sp_volchanged' system stored procedure after fulfilling any volume change request from the Backup Server. Backup Server: 4.124.2.1: Archive API error for device='SybGalaxy:: -file /opt/commvault/Base/Temp//sybGalaxyParams73573_0::000': Vendor application name= , Library version=0, API routine= , Message=Unable to open API library for device 'SybGalaxy:: -file /opt/commvault/Base/Temp//sybGalaxyParams73573_0'. Library path is '/sybase/ADQ/ASE-16_0/lib/libSybGalaxy.so'. dlopen() returned: Code=2, Message=/sybase/ADQ/ASE-16_0/lib/libSybGalaxy.so: cannot open shared object file: No such file or directory] Source: JMVXADSQAS00, Process: ClSybAgent

Hello Team,Support Portal is unavailable, again. It always seems to happen whenever I am in the middle of a Change that isn’t going to plan. I am beginning to take it personally :)