Virtualization and Containers

Hi All,I’m running 11.40.42 version and while restoring VM to OLVM 4.4.10.7 (RHV) I’ve encounter two issues:target VLAN has not been set correctly. Orginal VLAN has been preserved.  cross-hypervisor restore failed due to problems with attaching disk to VM. It looks like new VM does have Other OS type set instead of Oracle Linux which prevents attaching disk in SCSI mode. I’ve set additional attribute to not delete disk after failed restore and was able to create VM, attach disk and start VMI’m wondering if those two issues are releated and commvault has problems with restoring proper metadata? Anyone encounter similar issues?  

Hi, I’m chatting with Commvault chat bot and I have a question. Can someone explain what happens in the following case:I have a VM group that is assigned to Storage Policy X with deduplication, and incremental backups are running there with a synthetic full on Sundays. I then change the VM group’s Storage Policy to Y with a new deduplication database. The chat says that a new full backup is not triggered automatically—instead, incremental backups continue on the new storage.“The practical consequences for VM groups (virtualization, Index V2)—such as no automatic full, and the inability to restore from incrementals after a policy change—are documented mainly in Knowledge Base articles (KB62892, KB62688) and action_items.”However, those incrementals cannot be restored because the new database does not have a physical (true) full backup, and a synthetic full also cannot be created because there is no full.So why isn’t there any warning or information when changing the Storage Policy or Pl

Hi,I have some questions about the workflow for upgrading: VSA V1 to V2 Migration Workflow.In VMWare we have not only the defaultbackupSet but also many other backupSets where we sort different subclients.As far as I’ve understood, the backupSets are being considered legacy, and VMGroup can only be created it in the default backupset.What will happen to all of the subclients in the other backupsets under the client if I would run this workflow?Would they all go into the defaultBackupSet or would the new client maintain the structure of the backupSets and now VMGroups, even though they are not the defaultBackupSet. Does anyone have any experience with this? Kind regards,Daniel

Hello Team,Do we have any roadmap or update regarding VMware supportability on HPE VME?I reviewed the compatibility for version 11.32, and I do not see VMware listed as supported. However, could you please share any updates on the internal development roadmap for VMware support on HPE VME?Regards,Srini

Hi,We are decomissioning our VMware media agents and only using Azure hosted Median Agents. The new Azure Media Agents arent showing as access nodes for vcenter backups. I’ve read about installing VSA but cannot find the install files or an accurate guide to do this. All groups and software between old (vmware) and new (azure) media agents match. Thanks

Hi,Does Commvault have any roadmap to add support for Live VM Recovery for VMware running on Dell PowerFlex?TksFT

HiWe are trying to use Commvault for very large SQL Server VM (about 50 TB) running on Nutanix. The main requirement is to recover quickly after a security incident by restoring to a clean pre‑incident point while keeping RTO extremely low, which is hard when full database re‑hydration is required.Today, SQL point‑in‑time restores in Commvault appear to work in the traditional way: the database is rebuilt by streaming data from backup (full/diff) and then applying logs, writing out the entire MDF/NDF/LDF set again. For a 50 TB database, fully moving data from backup media back to production storage is not realistic for tight RTO objectives.What we would like is a workflow that:- Treats the SQL data disks (on Nutanix) more like snap‑based clones instead of full copy restores.  - Lets us promote or mount a snapshot at the individual disk/volume level, not only at whole‑VM level.  - Then uses Commvault only to apply transaction logs on top of that snapped data for point‑in‑time recovery,

Getting below error while trying guest file restore for a linux VM through access node in Commvault v11.40:“Browse failed due to error while mounting virtual machine: No valid node is available to perform a guest file restore of the choosen VM.” VM backup can be successful but browse/restore fails.Has anyone faced this kind of error befre? and what can we do to resolve this?

When I try to make a complete restore of a openstack’s instance, the response is : "errorMessage": "The particular hypervisor restore is not supported in API",Commserv version is : 11 SP36The request is : POST {{serverurl}}/V4/vm/the-correct-guid/restoreaccept: application/jsoncontent-type: application/jsonAuthtoken: {{auth_token}}{  "powerOnVmAfterRestore": true,  "overwriteVM": true,  "inPlaceRestore": true,  "fromtime": "2026-05-04T23:30:36",  "totime": "2026-05-04T23:36:26",  "vmDestinationInfo": {    "openstack": {    "openstackInstanceInfoList" : [        {           "sourceInstanceGuid" : "the-correct-guid",           "InstanceName" : "realname"        }       ]    }   } This instance is backuped successfully, and I can ask for details:GET {{serverurl}}/v4/virtualmachines/the-correct-guidaccept: application/jsonAuthtoken: {{auth_token}}{  "vmDetails": {    "displayName": "realname",    "summary": {      "hypervisor": {        "id": 747,        "name": "hypervisorname"      },   

Livesync est il possible entre deux proxmox VE?

Hi AllOvirt the Source project for OLVM is defaulting Keycloack as the Default Authentication Provider, so far Commvault doesn’t support it officially is there any workaround? or is the support coming soon? thanks 

Hi all.  When I tried to do a full vm restore of a Nutanix VM with inPlaceRestore and overwriteVM set to True (tried from both command center UI and API), The expected behavior in my mind is that the vm’s metadata (vm description, categories, and UUID) is kept after the restore, just like how a VMware full vm restore has been working for us. In our testing, the vm is deleted and then re-created, causing the VM UUID to change, at the same time, all the other vm metadata fields like description and categories are not restored; Guest Tool connection is broken because of the new UUID as well. Is this expected behavior? Could this have been caused by misconfiguration on VM Group/Hypervisor side?  Commvault 11.40Nutanix AHV 7.5 Thanks in advance!

Hi Team, We are backing up a VM(hosted on MS HyperV) whose data disk is located on a SMB NAS File share.We are getting below error.Error Code: [91:300] Description: Error creating virtual machine [VMNAME] snapshot. Please check the virtual machine snapshot tree and the hosting volume for free space. [Checkpoint operation for 'VMNAME' failed. (Virtual machine ID 83A8CX27-…….A4) Checkpoint operation for 'VMNAME' was cancelled. (Virtual machine ID 83A8CX27-…….A4) 'VMNAME' could not initiate a checkpoint operation: The process cannot access the file because it is being used by another process. (0x80070020). (Virtual machine ID 83A8CX27-…….A4) 'VMNAME' could not create auto virtual hard disk \\IP\Host\VM_Disk_3714DCEE-3E97-4364-A678-897EF9FE93F0.avhdx: The process cannot access the file because it is being used by another process. (0x80070020). (Virtual machine ID 83A8CX27-…….A4)]. Source: commserve, Process: JobManager I have verified in the HyperV Host event viewer, it is throwing error “

We are running a relatively new version of Ceph. In this newer Ceph release, the RBD commands used to create VM snapshots require specifying both the namespace and the keyring file to locate the VM disks. By contrast, Commvault locates VM disks using only the pool in its RBD command parameters. Commvault version 11.36 only supports older versions of Ceph.  

Hi,When will Nutanix AHV be supported by Commvault for version 10.3.0.2 and later ? According to the documentation, the latest supported version is currently 7.5.x.https://documentation.commvault.com/11.42/software/nutanix_ahv_system_requirements.htmlThe Commvault software is supported with Nutanix AHV versions 4.6, 4.7, 5.0, 5.1.x.x, 5.5.x.x, 5.6.x, 5.8.x, 5.9.x, 5.10.x, 5.11, 5.15, 5.16, 5.17.x, 5.18.x, 5.20.x, 6.0, 6.5, 6.7, 6.8, 6.10, 7.0.x, 7.3.x, and 7.5. Regards,Lukasz

Hi there,My name is Jim and I’m a Product Manager at OpenNebula - one of the most popular cloud management platforms on the market.We are an Open Source product and have a huge community of users, however in recent months we’ve had a huge influx of requests from our Enterprise Edition customers for Commvault VM backup support.I understand that in order to have this native integration it will need work from the Commvault team and perhaps you have some API standards we can implement on our side as well. We are willing to commit resources to assist and work on such an implementation and it would be great to open a discussion with the Commvault team on this.It would be great to hear if Commvault have had requests from their side as well - we would love to partner on this and share information on the Commvault / OpenNebula customers who have requested such an integration.Thanks in advance,Jim

Hi Commvault people,I am looking for feedback on Backup Copy throughput.We have a fairly new Commvault-AWS implementation.We have a few different DSP’s, with clients spread across several of the DSP’s.There is only one Media Agent, but we use Proxy’s in the other DSP’s.For example DSP1 has the MA and it’s attached library.DSP2 has a bunch of servers but only a VSA Proxy. Same for DSP 3 and 4 - clients and a VSA proxy but no Media Agent.So what we basically have is a cross-DSP configuration.The main media agent in DSP1 hosts the library.Clients are snapped in all of the other DSP’s using the VSa proxy who then streams the conetnts to the MA and it’s associated library.This is fully supportd and it seems to work well.However, I have noticed that although the Snap works fairly quickly (15 mins for a few servers), the Backup Copy is slower.  It will take a couple of hours to transfer a few hundred GB, averaging only 330ish GB/hr.So my question:-Is anyone else a cross-DSP backup solution an

Hello,We have multiple VMware VMs that were migrated between vCenters. The UUIDs of the VMs remained unchanged.In the Commvault console, we still see a single VM client; however, after the migration, a new Backup Set was created for the same VM.From a chargeback perspective, does this result in duplicate license consumption for these VMs?Thank you.

   We’re in the process of moving from VMware to Hyper‑V, and I’m seeing a pretty significant difference in IntelliSnap performance. Our Hyper‑V IntelliSnap jobs are averaging around 57 minutes, while the same workloads on VMware average 5 minutes.    Is this typical for Hyper‑V environments? I’d really like to hear what snapshot durations others are seeing with IntelliSnap on Hyper‑V.    Below is a chart comparing the two platforms. Each line represents a snapshot job. As you can see, the VMware jobs all complete within roughly an hour, while the Hyper‑V jobs stretch across a five‑hour window, which isn’t ideal for maintaining a tight RPO.Thank you, 

Does Commvault support NVMe-oF (NVMe over Fabrics, including NVMe over TCP)Arlie says:Commvault does not support NVMe-oF (NVMe over Fabrics, including NVMe over TCP) as a transport protocol for VMware VM backups. For VMFS datastores presented via NVMe-oF, you must use alternative, supported protocols for backup operations.Documentation (SAN Transport for VMware) NVMe-oF SAN is supported with VDDK 8.0.3 and higher using Linux access node only.I am a liitle bit confused now ….Regards,Thomas 

We have newly installed RHEL 10 servers for MediaAgents and we want to use them as VMWare Access Nodes. We have noticed that there is no documented support for VMware AccessNodes on RHEL 10 in docs. Does anyone know if there are any issues configuring these MA’s as Access Nodes for VMware at this point? /Patrik

Hello Commvault Community,I am currently working with Commvault version 11.42 and testing backup and recovery features for OpenShift Virtualization (KubeVirt).I have seen information stating that file-level restore for OpenShift Virtualization is not supported, but I have not been able to find this limitation officially documented.Could you please confirm whether file-level restore for VMs running on OpenShift Virtualization is indeed not supported in Commvault 11.42?If this is correct, can you share an official Commvault documentation link where this limitation is mentioned?Having this clarification and documentation would help us properly communicate the capabilities to our teams and customers.

I am receiving the following error in the backup of a Hyper-V VMError code: [91:148]Description: There are too many existing backup snapshots on virtual machine [ServerName]. Backup snapshots are being cleaned up, but manual intervention may be required to ensure that all snapshots are removed. This may indicate that the storage is unable to keep up with the I/O activity of the virtual machine during a backup.Source: cs0003, Process: JobManagerWhen I look in Hyper-V Manager, I see no checkpoints for this server, so I’m unsure how to resolve this.  I assume it’s possible it may resolve itself over time, but this has come up the last 2 backup cycles. 

Hi,  We got an error message on snapshot when we tried to backup a vm with a passthrough disk. We use xcp-ng as hypervisor (XenServer). We tried disk filter with the name and the path, we added the setting bEnableDiskFiltersForXen to true but nothing solve the problem  Last backup job [98] did not complete successfully for the VM group with error: Killed by admin. Reason:[]. Source: commserve01, Process: JobManager Unable to create a virtual machine snapshot of [test-backup01_rhel9]. [] Please check the virtual machine snapshot tree. Source: cv-proxy01, Process: vsbkpLast backup job [98] did not complete successfully for the VM group with error: Killed by admin. Reason:[]. Source: commserve01, Process: JobManager Unable to create a virtual machine snapshot of [test-backup01_rhel9]. [] Please check the virtual machine snapshot tree. Source: cv-proxy01, Process: vsbkp  We tried a backup with the same vm without the passtrough disk and it was successfull but removing the disk is not a via

We just started the implementation of Commvault in a brand new VMware environment. Now I'm seeing already an increased amount of duplicate client computers in our environment causing some administrative nightmares and management challenges.So I started investigating it and discovered the UUID registration to differ from what I'm used to when comparing it to AWS. It appears the registered UUID in Commvault is actually the so called PersistentID/InstanceUUID and this one can't be tracked back from within the VM itself. The UUID that is shown from the OS corresponds to the VMware BIOS UUID. We installed some client agents first followed by the configuration of the VSA agent. Both are being used actively. Fixing duplicate client names is an annoying tasks, especially in MSP environments and I'm puzzled this hasn't been fixed by Commvault. Because when you would use the combination of Commvault client name + BIOS UUID and the name that can be read by the client including UUID than matching