Hyper-V backup is failing with the error "avhypervvss Error <41719>: There are no targets eligible for backup" when Windows Server is using French locale
Summary: Hyper-V backup is failing with the error "avhypervvss Error <41719>: There are no targets eligible for backup" when Windows Server is using French locale
This article applies to
This article does not apply to
This article is not tied to any specific product.
Not all product versions are identified in this article.
Symptoms
Hyper-V backup is failing with the error: avhypervvss Error <41719>: There are no targets eligible for backup.
Relevant snippet from the backup log:
2018-12-11 09:50:08 avhypervvss Warning <43708>: GUID '#######' for target '<VM_NAME>' not matching with any available target(s) on the host(s)
2018-12-11 09:50:08 avhypervvss Warning <43709>: Target virtual machine '<VM_NAME><########>' is not matching to any available targets. Please check GUID and Target name against available targets on the host(s) Skipping from backup.
2018-12-11 09:50:08 avhypervvss Error <41719>: There are no targets eligible for backup
2018/12/11-08:50:08.57999 [hypervvss_assist] <=== hyperv_targets_base_manager::expand 641
2018-12-11 09:50:08 avhypervvss Error <41581>: Failed to backup targets. Unable to expand targets.
2018-12-11 09:50:08 avhypervvss Error <41662>: Failed to validate and expand the targets.
Relevant snippet from the backup log:
2018-12-11 09:50:08 avhypervvss Warning <43708>: GUID '#######' for target '<VM_NAME>' not matching with any available target(s) on the host(s)
2018-12-11 09:50:08 avhypervvss Warning <43709>: Target virtual machine '<VM_NAME><########>' is not matching to any available targets. Please check GUID and Target name against available targets on the host(s) Skipping from backup.
2018-12-11 09:50:08 avhypervvss Error <41719>: There are no targets eligible for backup
2018/12/11-08:50:08.57999 [hypervvss_assist] <=== hyperv_targets_base_manager::expand 641
2018-12-11 09:50:08 avhypervvss Error <41581>: Failed to backup targets. Unable to expand targets.
2018-12-11 09:50:08 avhypervvss Error <41662>: Failed to validate and expand the targets.
Cause
Due to French locale settings in Windows OS Hyper-V Plugin does not recognize VMs.
WMI query in Powershell is not returning any VM:
PS C:\Windows\system32>Get-WmiObject -Class Msvm_ComputerSystem -Namespace "root\virtualization\v2" -ComputerName <HYPER-V-NODE-NAME> | ? {$_.Caption -eq "Virtual Machine" } | select ElementName
PS C:\Windows\system32>
However, WMI query works if specify "Ordinateur virtuel"
PS C:\Windows\system32> Get-WmiObject -Class Msvm_ComputerSystem -Namespace "root\virtualization\v2" -ComputerName <HYPER-V-NODE-NAME> | ? {$_.Caption -eq "Ordinateur virtuel" } | select ElementName
ElementName
-----------
<VM_NAME_1>
<VM_NAME_2>
<VM_NAME_3>
WMI query in Powershell is not returning any VM:
PS C:\Windows\system32>Get-WmiObject -Class Msvm_ComputerSystem -Namespace "root\virtualization\v2" -ComputerName <HYPER-V-NODE-NAME> | ? {$_.Caption -eq "Virtual Machine" } | select ElementName
PS C:\Windows\system32>
However, WMI query works if specify "Ordinateur virtuel"
PS C:\Windows\system32> Get-WmiObject -Class Msvm_ComputerSystem -Namespace "root\virtualization\v2" -ComputerName <HYPER-V-NODE-NAME> | ? {$_.Caption -eq "Ordinateur virtuel" } | select ElementName
ElementName
-----------
<VM_NAME_1>
<VM_NAME_2>
<VM_NAME_3>
Resolution
Issue resolved in Avamar 19.2 and later releases.
Affected Products
Avamar ClientProducts
Avamar Client, Avamar Plug-in for Hyper-V VSSArticle Properties
Article Number: 000055472
Article Type: Solution
Last Modified: 22 Jul 2022
Version: 3
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.