Virtualization and Containers

Does Commvault support incremental backup for VMs having RAW disk in a OLVM set up ?

Hi. our setup Broadcom VCF9.1.1 cluster 10 hosts, one VSA per hosts. VSAN ESA. 2 VDS, one for VSAN the other for the rest including backup traffic.We are migrating from a standard VMware 8 cluster to VCF9.1.1Now we are starting to have issue in VCF9.1.1. VMK0 is crashing during backups. We a had to limit the number streams per CPU for the VSA from 10 to 3 to keep everything under control. Any tips? 

Dear can you please help me on this i am getting this on version running 11.28.68,Error Code: [91:145]Description: Unable to write data to the Virtual Disk [[NFS1] DENEUPRINT02_DR/DENEUPRINT02_DR.vmdk]. Please ensure that the proxy is able to communicate with the virtual machine host and that there is sufficient disk space available. Details: [One or more errors occurred while processing the request. (ERROR_ERRORS_ENCOUNTERED.774), Failed to write to vmdk (W32.774) (CV.0x1)]Source: deneucvma02, Process: vsrstNote: sufficient disk space is available

Hi everyone,We are currently facing a Commvault backup issue on Nutanix AHV.The initial problem was related to HotAdd / SCSI device detection on the Commvault Access Node. To fix that first issue, we had to add the following additional setting on the Access Node:VirtualServer\bEnableSCSIWLunDeviceCleaner = TrueAfter enabling EnableSCSIWLunDeviceCleaner, the initial HotAdd issue was resolved.The logs now confirm that the disk is correctly attached and opened:Disk [SCSI.0] is attached at [/dev/sdb]Opened [/dev/sdb] successfullyHowever, we are now facing a different issue when Commvault calls the Nutanix Data Protection APIs.The compute-changed-regions call returns:HTTP 401Invalid cookies present in the requestCommvault then reports:JWT Token has likely expired. Trying Discover cluster againDuring the new cluster discovery attempt, Nutanix returns:HTTP 429Failed to perform the operation as rate limit set by the API has been exceededPLAT-10003 - RATE_LIMIT_EXCEEDEDThen compute-changed-regi

Dear Team,We have configured the Nutanix Prism Element in the Metallic Commvault environment for VM backups.The configuration details are as follows:Nutanix Prism Element: Configured successfully in Commvault Nutanix User: Configured with User Admin, Cluster Admin, and Backup Admin roles Access Node: Configured within the Nutanix cluster for backup operations Connectivity: Validated successfully from the Access Node to the Nutanix Prism Element Ports Tested: TCP 9440, 2704, and 111 are reachable and working successfullyHowever, the VM backup is failing after approximately 20% progress with the following error:Error Code: [91:448]Error: Error opening the disks for virtual machine [abc]From the logs, we also observed the following errors: HTTP 401 - Authentication requiredHTTP 500 - Internal Server ErrorFailed to attach disk ... to proxyError opening the virtual machine disksWe have already validated the basic connectivity and the required ports from the Access Node to the Nutanix Prism

Environment: Commvault 11.44 CU16, Kubernetes (Virtual Server) agent. Storage is a CSI driver with a working default VolumeSnapshotClass (snapshot-controller running). What works:Regular streaming backup of a K8s application group succeeds. It creates a native CSI VolumeSnapshot, streams the data to the MediaAgent, then deletes the transient snapshot.What I'm trying to do:Retain the CSI VolumeSnapshot as the backup copy so that RESTORE provisions the PVC directly from the snapshot (volume clone), instead of streaming files into a new empty PVC.Reason: The streaming restore re-applies metadata to the restored PVC and leaves the volume mount-root as root:root 0000, which breaks non-root workloads (e.g. a Postgres/CNPG pod running as a non-root uid crash-loops). Restoring from the snapshot would preserve the original permissions.What I've tried and where it fails:- Enabled IntelliSnap on the K8s subclient. The ONLY snapshot engine offered is "Virtual Server Agent Snap".- Snap backup fails

Hi,we have 2 Problems:we are on Commvault 11.40.69. Proxmox 9.2.111)With https://lore.proxmox.com/all/6e3ffc1e-ccfc-4ec6-93f7-03bef79c8b78@proxmox.com/T/Proxmox needs Qemu Version 10 to support the Snapshot as Volume Chain.Is there a plan to support Qemu Version 10 ? With a Maintenance Release ? 2)A Restore of a Vmware VM to Proxmox work, but the Network Config is not converted.469908 72ba6 09/08 10:41:39 4661781 ProxmoxSDKWrapper::CProxmoxConnection::LogError() - Error: [] [400]. POST [https://du1devpve02.tq-net.de:8006/api2/json/nodes/du1devpve01/qemu/100/config]469908 72ba6 09/08 10:41:39 4661781 ProxmoxSDKWrapper::CProxmoxConnection::LogError() -   Err: [HTTP/1.1 400 Parameter verification failed.]469908 72ba6 09/08 10:41:39 4661781 ProxmoxSDKWrapper::CProxmoxConnection::LogError() -   Req: [net0=e1000%3D00%3A0c%3A29%3Aa5%3Ae2%3A5e%2Cbridge%3Dvds01-LBT%20%E2%80%93%20vlan586%20%E2%80%93%20srv-t1-linux%20-%2010.150.86.0-24%20%28vDS01%29]469908 72ba6 09/08 10:41:39 4661781 ProxmoxSDKW

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

Commvault / Nutanix AHV – HotAdd disk issue with Prism Element 7.5.1.10 (VOL-40301 / VOL-40302)Hello,We are currently troubleshooting a Commvault backup issue on a Nutanix AHV environment running Prism Element 7.5.1.10.The problem occurs during the disk HotAdd / mount operation on the Commvault VSA / Access Node.The communication with Nutanix Prism on TCP 9440 is working, but after the disk attachment operation, the Linux VSA does not detect the new device.Relevant Commvault log entries:CvProcess::system() - udevadm settle --timeout=30CvProcess::system() - Command completed with rc=0CDiskMapperLinux::PostAttachDisk() - Pausing to let device node appearCvSysfs::getNewDeviceName() - No new devices foundCvSysfs::getNewDeviceName() - No new devices foundCDiskMapperLinux::PostAttachDisk() -No new device found for disk id [<DISK_ID>]CPrismCentralInfo::MountVM_Disks() -DiskMapper PostAttach failed for disk [<DISK_ID>]We then receive an HTTP 404 from the Nutanix Volumes API:GEThttp

Good morning everyone, I wanted to ask whether CBT technology is used when backing up a VM on HPE Morpheus HVM to perform incremental backups, or whether each backup is effectively a full backup. Thank you.

Hi All,does somebody know when disk, or at least name filtering will become available for Proxmox and Nutanix VM backups?Ever so often VMs have disks assigned containing no content worth to be backed up. Like e.g. sources, lasrge test copies of developers or Update Vaults.With VMWare I am used to exclude such disks easily through disk filters, name filters or storage related ones. Or using the independent disk setting. For Nutanix and Proxmox I can find no such possibilities. Commvault also does not honor the Proxmox backup setting for disks.All filtering there applies to complete VMs only.Running currently 11.36.98, but also tested with 11.44.12.Thanks

Hi Commvault Community,We are backing up Proxmox Virtual Machines using Commvault.During the backup process, we observe that a snapshot is created on the Proxmox VM storage. The snapshot appears to consume storage space approximately equal to the VM disk size.For example:VM Disk Size: [300 GB] Proxmox Storage Type: [LVM-thin / ZFS / Ceph / NFS / iSCSI / Other] Commvault Access Node: Physical Server  Backup Type: Full / Incremental Storage Backend: [SAN/NAS/Local Storage]During the Commvault backup, the Proxmox snapshot is created on the same storage where the VM disk resides. We would like to understand:Is it expected behavior for the Proxmox snapshot created during a Commvault backup to consume storage close to the provisioned VM disk size? Does Commvault use a standard Proxmox snapshot or another snapshot mechanism? Is there a way to configure the snapshot to use a different storage location? Does Commvault support storage-level snapshots for Proxmox? What is the recommended configur

   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

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

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

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.

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,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