Ubuntu virtual machines on Microsoft Hyper-V hosts

[ald.plan]

Hello,

We have a Microsoft Hyper-V server with a mix of Windows and Linux virtual machines.
From the Veeam Backup and Replication (version 10), the Hyper-V host is registered as "Hyper-V standalone" host.
From the "INVENTORY" > "Microsoft Hyper-V" > "Standalone Hosts" panel, I can only see the Windows virtual machines, not the Linux virtual machines.

Is that normal?

Is it possible to backup Linux virtual machines in a similar way as Windows virtual machines?

[wishr]

Hi Ald,

You should be to view all the Linux VMs residing on a standalone host in the inventory pane and back them up the same way as any other VMs. Are you able to add your Linux VMs to a backup job using the top ribbon and clicking on Backup Job?

Thanks

[ald.plan]

Hi,

Thanks for the reply.

Unfortunately, I can't add the Linux VMs to a backup job using the top ribbon and clicking on Backup Job.
Sounds like I missed something somewhere.

Is there any requirements so that Linux VMs can be detected by VBR (except the fact that they are running)?

[Egor Yakovlev]

Greetings.
There are no special requirements for linux VMs to be visible.

Can you please clarify:
- what is your Hyper-V version
- exact VBR Build number
- is that Hyper-V a part of a failover cluster by chance?

/Thanks!

[ald.plan]

Hi,

Hyper-V host:
- OS: Windows 10 (1909)
- Hyper-V Manager version: 10.0.18362.1

VBR build number: 10.0.1.4854

We have actually several Hyper-V hosts but only one with Linux VMs.
So, as a test, I created a dummy Linux VM on another Hyper-V we have. In that case, the Linux VM appears well in the VBR console.

I guess I can tell the problem comes from the Hyper-V on which the original Linux VMs are running.
Is there any limit in the number of Hyper-V hosts that can be managed by VBR?
What kind of tests can I make to check the connectivity between VBR and the Hyper-V host?

Thanks

[wishr]

Hello,

Sounds suspicious. Are you using a paid VBR version or it is Community Edition? The only limit may be capacity of the license. What licensing information shows?

Regarding connectivity issues investigation, the best way to address them is by opening a support case with our support engineers. Honestly, I doubt the root cause is the connection because you can back up VMs from the same host.

Thanks

[Egor Yakovlev]

Expected behavior as Windows 10 with Hyper-V role aint't supported as a backup source platform.
/Thanks!

[ald.plan]

Expected behavior as Windows 10 with Hyper-V role aint't supported as a backup source platform.

This answers to my question. Indeed Windows 10 Hyper-V role is not supported.
The solution was to install a Linux agent on the VMs. Works fine and does the job.

Thanks.

[wishr]

Hi Ald,

Thanks for reporting back.

The use of Veeam Agents is a feasible workaround for this scenario.