Application-aware processing for linux guests?

[helman]

Is application-aware processing / indexing supported for linux guests?

It seems to try a login, but then fails with an error ( a localized one: Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt. )

for now I'll turn of application-awareness for linux guests - but I didn't find a mention if it's supposed to work on linux guests...

[Gostev]

No, as explained in the corresponding step of the wizard (see description on top of wizard) this is only supported for Microsoft Windows OS. You need to take different approach with Linux. Please be sure check sticky FAQ topic on top of this forum, as all of this is fully covered there.

[helman]

thanks - i knew I was missing something...

[johnwatson]

I know this is an old post, but I have fixed some of the errors when I have "Enable: Application-Aware Processing" is enabled for Linux guests on Hyper-V and Hyper-V Replication.

Environment: Windows Server 2019, Veeam Backup & Replication 11, Ubuntu 20.04
Here is a procedure I have created:

1. Run the Following commands and reboot when necessary:
- sudo apt-get update
- sudo apt-get upgrade
- sudo apt install mlocate
- sudo apt install linux-cloud-tools
- sudo apt install linux-cloud-lools-common
- sudo apt install linux-tools
- sudo apt install linux-tools-generic
- systemctl enable hv-kvp-daemon hv-vss-daemon hv-fcopy-daemon

2. Need to modify modules file
- sudo vi /etc/initramfs-tools/modules

Note: In vi Editor, navigate to the last line in the file and use the insert ( I ) command to append and enter the following lines:

hv_vmbus
hv_storvsc
hv_blkvsc
hv_netvsc

Note: Save the file by hitting the Esc key and then issuing the “: x” command

3. Finish up and commit the changes:
- sudo rmmod floppy
- sudo update-initramfs –u
- sudo shutdown -r now

4. Verify that Hyper-V Integrated tools are installed and working:
Note: From Linux Shell run the following command

- systemctl status hv-fcopy-daemon.service

Note: The Active Status should show Active now

Note: From powershell run the following

- Get-VMIntegrationService -vmname < VM Name >

e.g. Get-VMIntegrationService -vmname nextcloud

Note: Next to your VMName Key-Value Pair Exchange should read True OK
e.g. NEXTCLOUD Key- Value Pair Exchange True OK The protocol version of the component installed i.....

[johnwatson]

The Errors that it cleared up was:
Error 1:
Failed to create VM recovery checkpoint (mode: Veeam application-aware processing with failover) Details: Failed to create VM () recovery checkpoint. Job failed ('Checkpoint operation for '' failed. (Virtual machine ID )

Production checkpoints cannot be created for ''. (Virtual machine ID )'). Error code: '32770'.

Error 2:
Guest processing skipped (check guest OS VSS state and hypervisor integration components version)