03-10-2022 04:31 AM
Mar 9, 2022 8:04:35 PM - Info nbjm (pid=10620) starting backup job (jobid=99) for client LDC-01-VM, policy pc-vmware, schedule Cumulative-Inc
Mar 9, 2022 8:04:35 PM - Info nbjm (pid=10620) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=99, request id:{5F1707DC-101F-49FB-AFB6-D9511ACEE3D2})
Mar 9, 2022 8:04:35 PM - requesting resource nbumedia01-diskD-50T
Mar 9, 2022 8:04:35 PM - requesting resource nbumaster01.NBU_CLIENT.MAXJOBS.LDC-01-VM
Mar 9, 2022 8:04:35 PM - granted resource nbumaster01.NBU_CLIENT.MAXJOBS.LDC-01-VM
Mar 9, 2022 8:04:35 PM - granted resource MediaID=@aaaab;Path=D:\nbubak\;MediaServer=nbumedia01
Mar 9, 2022 8:04:35 PM - granted resource nbumedia01-diskD-50T
Mar 9, 2022 8:04:35 PM - estimated 10353742 kbytes needed
Mar 9, 2022 8:04:35 PM - begin Parent Job
Mar 9, 2022 8:04:35 PM - begin VMware:Step By Condition
Operation Status: 0
Mar 9, 2022 8:04:35 PM - end VMware:Step By Condition; elapsed time 0:00:00
Mar 9, 2022 8:04:35 PM - begin VMware:Read File List
Operation Status: 0
Mar 9, 2022 8:04:35 PM - end VMware:Read File List; elapsed time 0:00:00
Mar 9, 2022 8:04:35 PM - begin VMware:Create Snapshot
Mar 9, 2022 8:04:37 PM - started process bpbrm (pid=7356)
Mar 9, 2022 8:05:23 PM - Info bpbrm (pid=7356) LDC-01-VM is the host to backup data from
Mar 9, 2022 8:05:23 PM - Info bpbrm (pid=7356) reading file list for client
Mar 9, 2022 8:05:27 PM - Info bpbrm (pid=7356) start bpfis on client
Mar 9, 2022 8:05:27 PM - Info bpbrm (pid=7356) Starting create snapshot processing
Mar 9, 2022 8:05:33 PM - Info bpfis (pid=7732) Backup started
Mar 9, 2022 8:05:36 PM - snapshot backup of client LDC-01-VM using method VMware_v2
Mar 9, 2022 8:05:37 PM - Info bpbrm (pid=7356) INF - vmwareLogger: Creating snapshot for vCenter server 10.100.140.80, ESX host 10.100.140.60, BIOS UUID 564dc963-148c-749c-ce01-425206783301, Instance UUID 52908b85-2759-ec81-4695-2d36ac98c043, Display Name LDC-01-VM, Hostname LDC-01-VM.majnoon-ifms.com
Mar 9, 2022 8:05:37 PM - Info bpbrm (pid=7356) INF - vmwareLogger: Connection state of virtual machine: connected.
Mar 9, 2022 8:06:03 PM - Critical bpbrm (pid=7356) from client LDC-01-VM: FTL - vSphere_freeze: Snapshot task for virtual machine LDC-01-VM (/vmmor/vm-101) failed, 10 retries remaining, error type: 31, error message: Detected an invalid snapshot configuration..
Mar 9, 2022 8:06:54 PM - Critical bpbrm (pid=7356) from client LDC-01-VM: FTL - vSphere_freeze: Snapshot task for virtual machine LDC-01-VM (/vmmor/vm-101) failed, 9 retries remaining, error type: 31, error message: Detected an invalid snapshot configuration..
Mar 9, 2022 8:07:09 PM - end writing
Operation Status: 150
Mar 9, 2022 8:07:09 PM - end VMware:Create Snapshot; elapsed time 0:02:34
Mar 9, 2022 8:07:09 PM - begin VMware:Stop On Error
Operation Status: 0
Mar 9, 2022 8:07:09 PM - end VMware:Stop On Error; elapsed time 0:00:00
Operation Status: 150
Mar 9, 2022 8:07:09 PM - end Parent Job; elapsed time 0:02:34
Mar 9, 2022 8:07:29 PM - Critical bpbrm (pid=7356) from client LDC-01-VM: FTL - vSphere_freeze: Snapshot task for virtual machine LDC-01-VM (/vmmor/vm-101) failed, 8 retries remaining, error type: 31, error message: Detected an invalid snapshot configuration..
Mar 9, 2022 8:07:44 PM - Info bpfis (pid=0) done. status: 150: termination requested by administrator
termination requested by administrator (150)
03-10-2022 05:28 AM
Hello
please check with vm admins about this one
retries remaining, error type: 31, error message: Detected an invalid snapshot configuration..
Verify this configuration. Can vm admin do a snapshot of this given VM?
03-11-2022 01:20 AM
Get your VM admin to check this article and see if that fixes it https://kb.vmware.com/s/article/80246
03-15-2022 12:57 AM
I have seen this error in my environment when trying to restore VM's "Detected an invalid snapshot configuration" It turned out that that the SDN(Software Defined Networking) Team had been removing and recreating vDS (vSphere Distributed Switch). I got round it when restoring the VM by removing the networking from the restore. It created more work for the Cloud team but I will let them have the discussion with the SDN team :)