VM Name: abc5cbpapp002
|
TIME |
VM Name |
DOWN_TIME |
Host |
Location |
|
2019-10-12T15:25:34 |
abc9vdpapp013 |
0hr:0min:3sec |
esx-abc50esx20126 |
\esx-abc50esx20126.ABCD.com-2019-10-12–18.07-2831038\vmfs\volumes\5c361bfc-3d731eae-7937-f40343b931d0\abc9vdpapp013 |
|
2019-10-12T15:25:04 |
abc9vdpapp125 |
0hr:0min:5sec |
esx-abc50esx20177.ABCD.com |
\esx-abc50esx20177.ABCD.com-2019-10-12–18.21-2766523\vmfs\volumes\5c362386-2141d199-484f-f40343b931d0\abc9vdpapp125 |
Hostname: esx-abc50esx20126.ABCD.com
VMware ESXi 6.7.0
build-13644319
ESXi 6.7 EP 09
|
vmnic |
PCI bus address |
link |
speed |
duplex |
MTU |
driver |
driver version |
firmware version |
MAC address |
VID |
DID |
SVID |
SDID |
name |
|
vmnic0 |
0000:06:00.0 |
Up |
10000 |
Full |
1500 |
qfle3 |
1.0.77.2 |
7.15.56 |
d0:67:26:b2:10:b0 |
14e4 |
16a2 |
103c |
22fa |
QLogic Inc. QLogic 57840 10
Gigabit Ethernet Adapter |
|
vmnic1 |
0000:06:00.1 |
Up |
10000 |
Full |
1500 |
qfle3 |
1.0.77.2 |
7.15.56 |
d0:67:26:b2:10:b8 |
14e4 |
16a2 |
103c |
22fa |
QLogic Inc. QLogic 57840 10
Gigabit Ethernet Adapter |
VM Name: abc9vdpapp013
Time of Issue: 2019-10-12T15:25:34
Vmware Logs:
- From the Vmware logs we can see that the Virtual Machine is
undergoing a quiesce based snapshot from the Backup Application:
2019-10-12T15:25:13.308Z| vmx| I125:
VigorTransportProcessClientPayload: opID=6e4e49ee-93-6bac seq=214542: Receiving
Snapshot.Take request.
2019-10-12T15:25:13.317Z|
vmx| I125: SnapshotVMX_TakeSnapshot start:
‘RUBRIK-qn17EIG7Tsm0bgtxNcQA6A==-1c17f4de-659a-49d0-ae29-a40c16f68162’,
deviceState=0, lazy=0, quiesced=1, forceNative=0, tryNative=1,
saveAllocMaps=0
2019-10-12T15:25:13.323Z| vmx| I125:
DiskLib_IsVMFSSparseSupported: vmfssparse is not supported on
/vmfs/volumes/5c362366-f78db5a7-b3c0-f40343b931d0/abc9vdpapp013: f532.
2019-10-12T15:25:13.323Z|
vmx| I125: DISKLIB-LIB_CREATE : DiskLibCreateCreateParam:
Selecting the default child type as SeSparse for
/vmfs/volumes/5c362366-f78db5a7-b3c0-f40343b931d0/abc9vdpapp013/abc9vdpapp013-000001.vmdk.
2019-10-12T15:25:13.323Z|
vmx| I125: DISKLIB-LIB_CREATE :
DiskLibCreateCreateParam: seSparse grain size is set to 8 for
‘/vmfs/volumes/5c362366-f78db5a7-b3c0-f40343b931d0/abc9vdpapp013/abc9vdpapp013-000001.vmdk’
2019-10-12T15:25:13.324Z|
vmx| I125: DiskLib_IsVMFSSparseSupported: vmfssparse is not supported on
/vmfs/volumes/5c361bfc-3d731eae-7937-f40343b931d0/abc9vdpapp013: f532.
2019-10-12T15:25:13.324Z|
vmx| I125: DISKLIB-LIB_CREATE :
DiskLibCreateCreateParam: Selecting the default child type as SeSparse for
/vmfs/volumes/5c361bfc-3d731eae-7937-f40343b931d0/abc9vdpapp013/abc9vdpapp013_2-000001.vmdk.
2019-10-12T15:25:13.324Z|
vmx| I125: DISKLIB-LIB_CREATE :
DiskLibCreateCreateParam: seSparse grain size is set to 8 for
‘/vmfs/volumes/5c361bfc-3d731eae-7937-f40343b931d0/abc9vdpapp013/abc9vdpapp013_2-000001.vmdk’
2019-10-12T15:25:13.341Z|
vmx| I125: DiskLib_IsVMFSSparseSupported: vmfssparse is not supported on
/vmfs/volumes/5c361bfc-3d731eae-7937-f40343b931d0/abc9vdpapp013: f532.
2019-10-12T15:25:13.341Z|
vmx| I125: DISKLIB-LIB_CREATE :
DiskLibCreateCreateParam: Selecting the default child type as SeSparse for
/vmfs/volumes/5c361bfc-3d731eae-7937-f40343b931d0/abc9vdpapp013/abc9vdpapp013_1-000003.vmdk.
2019-10-12T15:25:13.341Z|
vmx| I125: DISKLIB-LIB_CREATE :
DiskLibCreateCreateParam: seSparse grain size is set to 8 for
‘/vmfs/volumes/5c361bfc-3d731eae-7937-f40343b931d0/abc9vdpapp013/abc9vdpapp013_1-000003.vmdk’
2019-10-12T15:25:13.341Z|
vmx| I125: SNAPSHOT: SnapshotPrepareTakeDoneCB: Prepare phase complete (The
operation completed successfully).
2019-10-12T15:25:13.397Z| vcpu-0| I125: ToolsBackup:
changing quiesce state: IDLE -> STARTED
2019-10-12T15:25:15.399Z|
vmx| I125: ToolsBackup: changing quiesce state: STARTED -> COMMITTED
2019-10-12T15:25:28.756Z| vcpu-0| A100: ConfigDB:
Setting scsi0:0.fileName = “abc9vdpapp013-000001.vmdk”
2019-10-12T15:25:28.757Z|
vcpu-0| A100: ConfigDB: Setting scsi0:1.fileName =
“/vmfs/volumes/5c361bfc-3d731eae-7937-f40343b931d0/abc9vdpapp013/abc9vdpapp013_2-000001.vmdk”
2019-10-12T15:25:28.757Z|
vcpu-0| A100: ConfigDB: Setting scsi0:2.fileName =
“/vmfs/volumes/5c361bfc-3d731eae-7937-f40343b931d0/abc9vdpapp013/abc9vdpapp013_1-000003.vmdk”
2019-10-12T15:25:28.789Z|
vcpu-0| I125: Checkpoint_Unstun: vm stopped for 13389663 us
2019-10-12T15:25:28.807Z| vcpu-0| I125: ToolsBackup:
changing quiesce state: COMMITTED -> FINISHING
2019-10-12T15:25:30.869Z|
vcpu-3| I125: ToolsBackup: changing quiesce state: IDLE -> DONE
2019-10-12T15:25:59.830Z|
vmx| I125: Guest: *** WARNING: GuestInfo collection interval longer than
expected; actual=60 sec, expected=30 sec. ***
2019-10-12T15:28:02.481Z| vmx| I125:
VigorTransportProcessClientPayload: opID=463981ca-c2-713a seq=215001: Receiving
Snapshot.Delete request.
2019-10-12T15:28:02.486Z| vmx| I125: SNAPSHOT:
SnapshotDeleteWork ‘/vmfs/volumes/5c362366-f78db5a7-b3c0-f40343b931d0/abc9vdpapp013/abc9vdpapp013.vmx’
: 2
2019-10-12T15:28:02.487Z|
vmx| I125: DISKLIB-VMFS :
“/vmfs/volumes/5c362366-f78db5a7-b3c0-f40343b931d0/abc9vdpapp013/abc9vdpapp013-000001-sesparse.vmdk”
: open successful (5) size = 231743488, hd = 0. Type 19
2019-10-12T15:28:02.487Z|
vmx| I125: DISKLIB-VMFS :
“/vmfs/volumes/5c362366-f78db5a7-b3c0-f40343b931d0/abc9vdpapp013/abc9vdpapp013-000001-sesparse.vmdk”
: closed.
2019-10-12T15:28:02.488Z|
vmx| I125: DISKLIB-VMFS :
“/vmfs/volumes/5c362366-f78db5a7-b3c0-f40343b931d0/abc9vdpapp013/abc9vdpapp013-flat.vmdk”
: open successful (5) size = 53687091200, hd = 0. Type 3
2019-10-12T15:28:02.488Z|
vmx| I125: DISKLIB-VMFS :
“/vmfs/volumes/5c362366-f78db5a7-b3c0-f40343b931d0/abc9vdpapp013/abc9vdpapp013-flat.vmdk”
: closed.
2019-10-12T15:28:02.488Z|
vmx| I125: DISKLIB-VMFS :
“/vmfs/volumes/5c361bfc-3d731eae-7937-f40343b931d0/abc9vdpapp013/abc9vdpapp013_2-000001-sesparse.vmdk”
: open successful (5) size = 193990656, hd = 0. Type 19
2019-10-12T15:28:02.488Z|
vmx| I125: DISKLIB-VMFS :
“/vmfs/volumes/5c361bfc-3d731eae-7937-f40343b931d0/abc9vdpapp013/abc9vdpapp013_2-000001-sesparse.vmdk”
: closed.
2019-10-12T15:28:02.488Z|
vmx| I125: DISKLIB-VMFS :
“/vmfs/volumes/5c361bfc-3d731eae-7937-f40343b931d0/abc9vdpapp013/abc9vdpapp013_2-flat.vmdk”
: open successful (5) size = 44023414784, hd = 0. Type 3
2019-10-12T15:28:02.488Z|
vmx| I125: DISKLIB-VMFS :
“/vmfs/volumes/5c361bfc-3d731eae-7937-f40343b931d0/abc9vdpapp013/abc9vdpapp013_2-flat.vmdk”
: closed.
2019-10-12T15:28:02.489Z|
vmx| I125: DISKLIB-VMFS :
“/vmfs/volumes/5c361bfc-3d731eae-7937-f40343b931d0/abc9vdpapp013/abc9vdpapp013_1-000003-sesparse.vmdk”
: open successful (5) size = 443801600, hd = 0. Type 19
2019-10-12T15:28:02.489Z|
vmx| I125: DISKLIB-VMFS :
“/vmfs/volumes/5c361bfc-3d731eae-7937-f40343b931d0/abc9vdpapp013/abc9vdpapp013_1-000003-sesparse.vmdk”
: closed.
2019-10-12T15:28:02.489Z|
vmx| I125: DISKLIB-VMFS :
“/vmfs/volumes/5c361bfc-3d731eae-7937-f40343b931d0/abc9vdpapp013/abc9vdpapp013_1-flat.vmdk”
: open successful (5) size = 107374182400, hd = 0. Type 3
2019-10-12T15:28:02.489Z|
vmx| I125: DISKLIB-VMFS :
“/vmfs/volumes/5c361bfc-3d731eae-7937-f40343b931d0/abc9vdpapp013/abc9vdpapp013_1-flat.vmdk”
: closed.
2019-10-12T15:28:02.507Z|
vmx| I125: SNAPSHOT: SnapshotDeleteFile deleted
‘/vmfs/volumes/5c362366-f78db5a7-b3c0-f40343b931d0/abc9vdpapp013/abc9vdpapp013-quiesce_manifest2.xml’.
2019-10-12T15:28:02.519Z|
vmx| I125: VigorTransport_ServerSendResponse opID=463981ca-c2-713a seq=215001:
Completed Snapshot request.
2019-10-12T15:28:02.521Z|
vmx| I125: VigorTransportProcessClientPayload: opID=463981ca-c2-713a
seq=215002: Receiving Snapshot.Consolidate request.
2019-10-12T15:28:02.523Z|
vmx| I125: SnapshotVMX_Consolidate: Starting online snapshot consolidate
operation.
2019-10-12T15:28:02.563Z| vcpu-0| I125:
Checkpoint_Unstun: vm stopped for 34773 us
- Phase in which we are facing the issue is while coming the Quiesce
state for the VM.
2019-10-12T15:25:13.397Z| vcpu-0| I125: ToolsBackup:
changing quiesce state: IDLE -> STARTED
2019-10-12T15:25:15.399Z|
vmx| I125: ToolsBackup: changing quiesce state: STARTED -> COMMITTED
2019-10-12T15:25:28.756Z| vcpu-0| A100: ConfigDB:
Setting scsi0:0.fileName = “abc9vdpapp013-000001.vmdk”
2019-10-12T15:25:28.757Z|
vcpu-0| A100: ConfigDB: Setting scsi0:1.fileName =
“/vmfs/volumes/5c361bfc-3d731eae-7937-f40343b931d0/abc9vdpapp013/abc9vdpapp013_2-000001.vmdk”
2019-10-12T15:25:28.757Z|
vcpu-0| A100: ConfigDB: Setting scsi0:2.fileName =
“/vmfs/volumes/5c361bfc-3d731eae-7937-f40343b931d0/abc9vdpapp013/abc9vdpapp013_1-000003.vmdk”
2019-10-12T15:25:28.789Z|
vcpu-0| I125: Checkpoint_Unstun: vm stopped for 13389663 us
2019-10-12T15:25:28.807Z| vcpu-0| I125: ToolsBackup:
changing quiesce state: COMMITTED -> FINISHING
2019-10-12T15:25:30.869Z|
vcpu-3| I125: ToolsBackup: changing quiesce state: IDLE -> DONE
Tools Version:
2019-10-10T15:37:25.831Z| vmx| I125: Guest: toolbox:
Version: 10.3.2.6765 (build-9925305)
2019-10-10T15:39:57.580Z| vmx| I125: Guest: toolbox: Version: 10.3.5.7752
(build-10430147)
Hostd Logs:
2019-10-12T15:25:13.307Z info hostd[2099913]
[Originator@6876 sub=Vimsvc.TaskManager opID=6e4e49ee-93-6bac user=vpxuser:ABCD\svcUSADMINBUVCB]
Task Created : haTask-72-vim.VirtualMachine.createSnapshot-792588
2019-10-12T15:25:13.308Z
info hostd[2100350] [Originator@6876
sub=Vmsvc.vm:/vmfs/volumes/5c362366-f78db5a7-b3c0-f40343b931d0/abc9vdpapp013/abc9vdpapp013.vmx
opID=6e4e49ee-93-6bac user=vpxuser:ABCD\svcUSADMINBUVCB] State Transition
(VM_STATE_ON -> VM_STATE_CREATE_SNAPSHOT)
2019-10-12T15:25:28.808Z info hostd[2584925] [Originator@6876
sub=Vmsvc.vm:/vmfs/volumes/5c362366-f78db5a7-b3c0-f40343b931d0/abc9vdpapp013/abc9vdpapp013.vmx]
Send config update invoked
2019-10-12T15:25:28.885Z warning hostd[2584925] [Originator@6876
sub=Vmsvc.vm:/vmfs/volumes/5c362366-f78db5a7-b3c0-f40343b931d0/abc9vdpapp013/abc9vdpapp013.vmx]
File – failed to get objectId,
‘/vmfs/volumes/5c362366-f78db5a7-b3c0-f40343b931d0/abc9vdpapp013/abc9vdpapp013.vmx’:
Operation not supported (11)
2019-10-12T15:25:30.901Z info hostd[2287501] [Originator@6876
sub=Vmsvc.vm:/vmfs/volumes/5c362366-f78db5a7-b3c0-f40343b931d0/abc9vdpapp013/abc9vdpapp013.vmx]
Send config update invoked
2019-10-12T15:25:30.949Z
warning hostd[2287501] [Originator@6876
sub=Vmsvc.vm:/vmfs/volumes/5c362366-f78db5a7-b3c0-f40343b931d0/abc9vdpapp013/abc9vdpapp013.vmx]
File – failed to get objectId,
‘/vmfs/volumes/5c362366-f78db5a7-b3c0-f40343b931d0/abc9vdpapp013/abc9vdpapp013.vmx’:
Operation not supported (11)
2019-10-12T15:25:30.981Z
info hostd[2287501] [Originator@6876
sub=Vmsvc.vm:/vmfs/volumes/5c362366-f78db5a7-b3c0-f40343b931d0/abc9vdpapp013/abc9vdpapp013.vmx]
State Transition (VM_STATE_CREATE_SNAPSHOT -> VM_STATE_ON)
2019-10-12T15:28:02.577Z info hostd[2100349]
[Originator@6876
sub=Vmsvc.vm:/vmfs/volumes/5c362366-f78db5a7-b3c0-f40343b931d0/abc9vdpapp013/abc9vdpapp013.vmx]
Send config update invoked
2019-10-12T15:28:17.338Z info hostd[2100360] [Originator@6876
sub=Vmsvc.vm:/vmfs/volumes/5c362366-f78db5a7-b3c0-f40343b931d0/abc9vdpapp013/abc9vdpapp013.vmx]
Send config update invoked
2019-10-12T15:28:17.411Z
warning hostd[2100360] [Originator@6876
sub=Vmsvc.vm:/vmfs/volumes/5c362366-f78db5a7-b3c0-f40343b931d0/abc9vdpapp013/abc9vdpapp013.vmx]
File – failed to get objectId,
‘/vmfs/volumes/5c362366-f78db5a7-b3c0-f40343b931d0/abc9vdpapp013/abc9vdpapp013.vmx’:
Operation not supported (11)
2019-10-12T15:28:18.483Z
info hostd[2099390] [Originator@6876
sub=Vmsvc.vm:/vmfs/volumes/5c362366-f78db5a7-b3c0-f40343b931d0/abc9vdpapp013/abc9vdpapp013.vmx]
Send config update invoked
2019-10-12T15:28:18.535Z warning hostd[2099390] [Originator@6876
sub=Vmsvc.vm:/vmfs/volumes/5c362366-f78db5a7-b3c0-f40343b931d0/abc9vdpapp013/abc9vdpapp013.vmx]
File – failed to get objectId,
‘/vmfs/volumes/5c362366-f78db5a7-b3c0-f40343b931d0/abc9vdpapp013/abc9vdpapp013.vmx’:
Operation not supported (11)
2019-10-12T15:28:19.126Z
info hostd[2584925] [Originator@6876
sub=Vmsvc.vm:/vmfs/volumes/5c362366-f78db5a7-b3c0-f40343b931d0/abc9vdpapp013/abc9vdpapp013.vmx]
State Transition (VM_STATE_REMOVE_SNAPSHOT -> VM_STATE_ON)
VMKernel Logs:
2019-10-12T13:11:28.902Z cpu6:2802188)MemSchedAdmit:
471: Admission failure in path: vm.2802183/vmmanon.2802183
2019-10-12T13:11:28.902Z cpu0:2802184)MemSchedAdmit: 471: Admission failure in
path: vm.2802183/vmmanon.2802183
2019-10-12T18:11:37.841Z
cpu7:2833673)WARNING: LinuxThread: 423: sfcb-intelcim: Error cloning thread: -1
(bad0117)
2019-10-12T18:11:37.842Z
cpu7:2833673)WARNING: LinuxThread: 423: sfcb-intelcim: Error cloning thread: -1
(bad0117)
2019-10-12T18:11:37.842Z
cpu7:2833673)WARNING: LinuxThread: 423: sfcb-intelcim: Error cloning thread: -1
(bad0117)
- Checked another Esxi Host to understand the issue:
Hostname: esx-abc50esx20177.ABCD.com
VM Name: abc9vdpapp125
Time of Issue: 2019-10-12T15:25:04
Vmware Logs:
- Found that the Snapshot operation was going on this Esxi Host as
well.
2019-10-12T15:22:11.337Z| vmx| I125:
VigorTransportProcessClientPayload: opID=76fa1187-ac-432d seq=521821: Receiving
Snapshot.Take request.
2019-10-12T15:22:11.348Z|
vmx| I125: SnapshotVMX_TakeSnapshot start:
‘RUBRIK-qn17EIG7Tsm0bgtxNcQA6A==-a0e6fcf8-ac6f-4494-a41f-89fbc9483b4a’,
deviceState=0, lazy=0, quiesced=1, forceNative=0, tryNative=1, saveAllocMaps=0
2019-10-12T15:22:11.354Z|
vmx| I125: DiskLib_IsVMFSSparseSupported: vmfssparse is not supported on
/vmfs/volumes/5c362386-2141d199-484f-f40343b931d0/abc9vdpapp125: f532.
2019-10-12T15:22:11.354Z|
vmx| I125: DISKLIB-LIB_CREATE :
DiskLibCreateCreateParam: Selecting the default child type as SeSparse for
/vmfs/volumes/5c362386-2141d199-484f-f40343b931d0/abc9vdpapp125/abc9vdpapp125_3-000001.vmdk.
2019-10-12T15:22:11.402Z| vcpu-0| I125: ToolsBackup:
changing quiesce state: IDLE -> STARTED
2019-10-12T15:22:13.407Z|
vmx| I125: ToolsBackup: changing quiesce state: STARTED -> COMMITTED
2019-10-12T15:22:14.301Z| vcpu-0| I125:
Checkpoint_Unstun: vm stopped for 894010 us
2019-10-12T15:22:14.318Z| vcpu-0| I125: ToolsBackup:
changing quiesce state: COMMITTED -> FINISHING
2019-10-12T15:22:16.355Z|
vcpu-0| I125: ToolsBackup: changing quiesce state: IDLE -> DONE
2019-10-12T15:24:46.728Z|
vcpu-0| I125: Checkpoint_Unstun: vm stopped for 27868 us
2019-10-12T15:24:55.856Z| vcpu-0| I125:
Checkpoint_Unstun: vm stopped for 8125885 us
2019-10-12T15:24:56.712Z| vcpu-0| I125: DumpDiskInfo:
scsi0:0 createType=11, capacity = 104857600, numLinks = 1, allocationType = 1
2019-10-12T15:24:56.713Z|
vcpu-0| I125: DISKLIB-LINK : Opened
‘/vmfs/volumes/5c362386-2141d199-484f-f40343b931d0/abc9vdpapp125/abc9vdpapp125_1.vmdk’
(0xa): vmfs, 85983232 sectors / 41 GB.
2019-10-12T15:24:56.715Z|
vcpu-0| I125: DumpDiskInfo: scsi0:1 createType=11, capacity = 85983232,
numLinks = 1, allocationType = 1
2019-10-12T15:24:56.716Z|
vcpu-0| I125: DISKLIB-LINK : Opened
‘/vmfs/volumes/5c362386-2141d199-484f-f40343b931d0/abc9vdpapp125/abc9vdpapp125_2-000001.vmdk’
(0x8): seSparse, 209715200 sectors / 100 GB.
2019-10-12T15:24:56.721Z|
vcpu-0| I125: DISKLIB-LINK : Opened
‘/vmfs/volumes/5c362386-2141d199-484f-f40343b931d0/abc9vdpapp125/abc9vdpapp125_2.vmdk’
(0x20a): vmfs, 209715200 sectors / 100 GB.
2019-10-12T15:24:57.146Z| vcpu-0| I125: Vix:
[mainDispatch.c:4239]: VMAutomation_ReportPowerOpFinished: statevar=3,
newAppState=1881, success=1 additionalError=0
2019-10-12T15:25:14.792Z|
vcpu-0| I125: HBACommon: First write on
scsi0:1.fileName=’/vmfs/volumes/5c362386-2141d199-484f-f40343b931d0/abc9vdpapp125/abc9vdpapp125_1.vmdk’
2019-10-12T15:25:14.793Z|
vcpu-0| I125: DDB: “longContentID” =
“34aef877322cb7c5ab6424881980d1eb” (was
“64a53c45a76c8577a04ab7042904c03d”)
2019-10-12T15:25:14.808Z|
vcpu-0| I125: DISKLIB-CHAIN : DiskChainUpdateContentID: old=0x2904c03d,
new=0x1980d1eb (34aef877322cb7c5ab6424881980d1eb)
2019-10-12T15:25:15.928Z|
vcpu-0| I125: HBACommon: First write on
scsi0:2.fileName=’/vmfs/volumes/5c362386-2141d199-484f-f40343b931d0/abc9vdpapp125/abc9vdpapp125_2.vmdk’
2019-10-12T15:25:15.928Z|
vcpu-0| I125: DDB: “longContentID” =
“e5b94c1eab2a343940cff63ec9539333” (was
“1b8415e9975b6fd29c928aff1f63bddf”)
2019-10-12T15:25:15.942Z|
vcpu-0| I125: DISKLIB-CHAIN : DiskChainUpdateContentID: old=0x1f63bddf,
new=0xc9539333 (e5b94c1eab2a343940cff63ec9539333)
2019-10-12T16:18:11.989Z|
svga| I125: MKSScreenShotMgr: Taking a screenshot
2019-10-12T16:20:03.377Z|
svga| I125: MKSScreenShotMgr: Taking a screenshot
Quiesce: If the flag is 1 or true, and the virtual machine is powered on when the
snapshot is taken, VMware Tools is used to quiesce the file system in the
virtual machine. Quiescing a file system is a process of bringing the on-disk
data of a physical or virtual computer into a state suitable for backups. This
process might include such operations as flushing dirty buffers from the
operating system’s in-memory cache to disk, or other higher-level
application-specific tasks.
Note: Quiescing indicates pausing or altering the state of running processes
on a computer, particularly those that might modify information stored on disk
during a backup, to guarantee a consistent and usable backup. Quiescing is not
necessary for memory snapshots; it is used primarily for backups.
Conclusion:
- From the
Logs we can see that the issue is happening while we are taking backup of
the VMs with Quiesce enabled. This could be an issue either with the
Sensitive VMs unable to handle the Delay while the OS is in freeze State.
- Please
check and test by taking backup of a VM without Quiesce and check the
status.
- Please
check from the logs inside the VM if there is any Failures during this
operation.
As discussed earlier please run
the ESXTOP with the below commands to review the logs from the Performance
standpoint.
esxtop -b -d 600 -n 3
>/var/volume/<Datastore Name>/esxtstats.csv
600 * 3 =
1,800 Seconds :
Please Note that this is requires a good amount of space, so please use a datastore
which has a good amount of free space available.
