Problem with Application aware processing

[xrated]

Hello

i am using community edition u4. VBR is running on 2019 std, Hyper-V server is free 2016 core edition without beeing member in AD (workgroup mode).

While i can backup vm with guest quiescence with no problem, i am getting error on all vms during test in guest processing tab with application aware processing enabled. I havent tried to backup with this settings due to the error during test.

Code: Select all

21.03.2019 11:29:02 :: Finding VM reference on host hyperv 
21.03.2019 11:29:02 :: VM reference: 1ecee5c9-687f-4ec3-bfd8-552e6c9c53a8
21.03.2019 11:29:02 :: Collecting guest OS info.
21.03.2019 11:29:03 :: VM is powered on.
21.03.2019 11:29:03 :: IP addresses: 192.168.3.13
21.03.2019 11:29:03 :: Guest OS: Microsoft Windows Server 2019 (1809)
21.03.2019 11:29:03 :: Checking standard credentials <- has exclamation mark
21.03.2019 11:29:03 :: Connecting to guest OS via RPC
21.03.2019 11:29:03 :: Testing admin share accessibility via RPC
21.03.2019 11:29:03 :: Testing guest OS connectivity via RPC
21.03.2019 11:29:04 :: Connecting to guest OS via PowerShell Direct <- red X beginning here
21.03.2019 11:29:04 :: Testing admin share accessibility via PowerShell Direct
21.03.2019 11:29:04 ::  Error code: 0x80131500;
21.03.2019 11:29:04 :: Failed to connect to guest VM: Unknown error 0x80131500. Cannot connect to VM [1ecee5c9-687f-4ec3-bfd8-552e6c9c53a8] over PSDirect. Guest Login: [DOMAIN\Administrator].;
21.03.2019 11:29:04 :: Failed to invoke func [Connect]: Unknown error 0x80131500. Unknown error 0x80131500. PowerShell 2.0 or later is required.;
21.03.2019 11:29:04 :: COM error:  Code: 0x80131500;

I found:
https://www.veeam.com/de/kb1855

when i run on hyper-v: Get-VM | ft Name, IntegrationServicesVersion
i get version 0.0

But integration services are already included in Server OS since a long time. On VM IntegrationServicesVersion is 10.0.17763

[wishr]

Hi Thomas,

Have you had a chance to raise a support ticket? If so, please let us know the ticket (case) number you got. I suppose the root cause is missing Power Shell 2.0 on the Hyper-V server that can be installed using Server Manager - it might be a good idea to check this out first.

Regards,
Fedor

[xrated]

Hello Fedor

brilliant, i didnt know it needs exact version 2.0, now its working

i am eligable to open ticket with community edition?

if i set application aware processing for one vm to VSS disable and enable Hyper-V guest quiescence in options then it will really use the latter option for that vm ?
i am not sure if i can specify all vm in one backup job containing linux and windows vms.

And if Take crash consistent backup is enabled, i need to install integration services on linux or open-vm-tools?

[nmdange]

For Linux VMs, you'll want to look up your distro/version here:
https://docs.microsoft.com/en-us/window ... on-windows

Then see whether LIS is required, and see if there are any additional requirements under "Live virtual machine backup". In cases where LIS is built-in, you typically needs to install an additional package like "hyperv-daemons"

[wishr]

Hi Thomas,

Please find the answers below.

1. Yes, even with Community Edition you can still open up a case and get best effort support (see pg.6 of Veeam Support Policy).
2. Hyper-V guest quiescence can be only used for VMs with AAIP disabled/unavailable for some reason. It will really use the latter option, but only if AAIP is disabled (on the "General" tab) for that specific VM (or has failed). Here is a description of how it works.
3. Yes, It is possible to specify both Windows and Linux VMs in a single job, activate Hyper-V guest quiescence at the job level, but ensure that all VMs supporting VSS have AAIP enabled for each of them on the "General" tab.

@Nmdamage, thanks, good point!

Regards,
Fedor

[xrated]

I installed hyperv-daemon on Debian, now in Application aware processing it tells "Debian 8 64" is not supported (before it was ip not resolved). Is that true because only the guest quiscence option is supported on Linux? I am wondering because hyperv-daemon seems to enable VSS. And how do i know if i have to use online, offline or crash consistent (veeam method) and which one is best?

Whats behind the crash consistent option? Is it only preventing shutdown or is it different technique then guest quiescence?

documentation is really bit too short: https://helpcenter.veeam.com/docs/backu ... l?ver=95u4

Edit: i had wrong user on linux vm credentials, now it shows ok. Now even more confused, should display something like denied, not "OS not supported" if wrong user is select

[wishr]

Basically, Online and Offline options guarantee transaction consistency, while Crash-consistent option does not (the same applies to the integrity of open files). You may find more information on all the options by the link above and in my previous post.

Regarding the error message - thanks for reporting this behavior. We'll see what can be improved.

Regards,
Fedor

[xrated]

I had Windows user set on linux vm. I was not able to change user by selecting "Set User", it was not changing.
Was only possible by pressing on "Default std credentials" button.
It was also not chaning pressing on "Default linux credentials"!

Default button is also confusing, because its not really clear who is default user for standard or linux credentials. Default standard credentials is selected on "Guest OS credentials" section in guest processing? Why there are 3 root accounts predefined? I created 4th one for my linux vm because i couldnt select any by "set user". I am also not able to remove the created linux account even if it is not selected in credentials.

[wishr]

Not sure what was wrong here and why it was impossible to set the user - it might be better to discuss this behavior with the support team (personally, I was not able to reproduce that). Accounts can be centrally managed through the Credentials Manager, accessible via the "Manage Accounts" button on the Guest Processing step. The three root accounts probably have been added by somebody before - B&R comes with no predefined accounts of course. The default account is the one set on the job level, in the Guest OS credentials section - this maybe requires a better clarification in the documentation - we'll see what can be improved here.