Skip to main content

VMware AppAware Backup Jobs Stuck in Queued Status Due to Leftover Guest OS Processes

VMware AppAware Backup Jobs Stuck in Queued Status Due to Leftover Guest OS Processes

Problem Description

VMware AppAware backup jobs may suddenly remain in a Queued status, causing subsequent scheduled backup jobs to be skipped or exceed their allocated backup window.

This behavior occurs when leftover or hung guest plugin processes (such as PhoenixSQLGuestPlugin.exe or PhoenixSQLGuestPluginRestore.exe) remain running inside the target Virtual Machine (Guest OS), preventing new backup or restore operations from initializing properly.

Cause

Leftover, hung, or orphaned processes from previous or failed jobs remain active within the target VM's Guest OS. These processes hold resource locks or interfere with guest communication, preventing new AppAware backup and restore jobs from starting.

Resolution

To resolve this issue, perform the following steps to terminate the hung processes:

  1. Log in to the target Virtual Machine's Guest OS (Windows).

  2. Open Task Manager.

  3. Check the Processes tab for any lingering Druva processes, such as:

    • PhoenixSQLGuestPlugin.exe

    • PhoenixSQLGuestPluginRestore.exe

  4. Right-click any stuck or leftover processes and select End task.

  5. To prevent security software from interrupting or hanging these processes in the future, ensure the appropriate Antivirus/Firewall exclusions are configured as detailed in the Firewall, Antivirus, and Network Configuration for Druva Enterprise Workloads guide.

Include and Exclude Filters

Ensure that PhoenixSQLGuestPlugin.exe and PhoenixSQLGuestPluginRestore.exe are added to the exclusion list of any local Firewall or Antivirus software running inside the Guest OS.

Verification

Follow these steps to verify that the issue has been resolved:

  1. Open Task Manager on the Guest OS to confirm no orphaned PhoenixSQLGuestPlugin*.exe processes are running.

  2. Confirm that local firewall and antivirus exclusions are actively applied on the target VM.

  3. Check the Druva Management Console to ensure the backup proxy status displays as Connected.

  4. Trigger a manual backup job for a test virtual machine.

  5. Monitor the job status in the console to ensure it transitions successfully from Queued to In Progress and completes successfully.

See Also

Did this answer your question?