OADP backup of Windows VMs ends with PartiallyFailed status

Environment

• OpenShift Container Platform (OCP) 4.16.5
• OpenShift Virtualization 4.16
• OpenShift API for Data Protection (OADP) 1.4.1
• Microsoft Windows Server 2016, 2022 VMs
  • QEMU Guest Agent 108.0.1

Issue

• The backup jobs of the Windows Server VMs running in a OpenShift cluster end with PartiallyFailed status.

• In the backup logs we see that the Freeze command failed:

  command Freeze failed: LibvirtError(Code=86, Domain=10, Message='Guest agent is not responding: Guest agent not available for now')
  

Root Cause

The guest-fsfreeze-freeze guest agent call returns an error 1:

$ oc exec virt-launcher-windows-2k22-virtio-crimson-worm-76-z4mhk -- virsh qemu-agent-command 1 '{"execute": "guest-fsfreeze-freeze"}'
error: Guest agent is not responding: Guest agent not available for now
command terminated with exit code 1

The issue has been reported and is being investigated in the bug This content is not included.CNV-54193.

Diagnostic Steps

• Make sure that the qemu-guest-agent is up to date and running.
• Run the fsfreeze call in the pod to confirm if it returns an error:

$ oc exec virt-launcher-windows-2k22-virtio-crimson-worm-76-z4mhk -- virsh qemu-agent-command 1 '{"execute": "guest-fsfreeze-freeze"}'
error: Guest agent is not responding: Guest agent not available for now
command terminated with exit code 1

$ oc exec virt-launcher-windows-2k22-virtio-crimson-worm-76-z4mhk -- virsh qemu-agent-command 1 '{"execute": "guest-fsfreeze-status"}'
{"return":"frozen"}

$ oc exec virt-launcher-windows-2k22-virtio-crimson-worm-76-z4mhk -- virsh qemu-agent-command 1 '{"execute": "guest-fsfreeze-thaw"}'
{"return":3}

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.