Strange behaviour on ReFS

[showiproute]

Hello everyone,

I have been using Veeam B&R since today on a central Windows Server 2019 VM (updated ESXi 6.7).

As a backup job beside a few others I have added a file based back up from my local Workstation (Win 10 Pro for Workstation).
Following things I have recognized when doing a backup:

(both drives are NVMe SSDs, so should have enough speed)
C drive (NTFS) - backs up at ~450 MB/s; I have enabled "Backup OS"
E drive (ReFS) - backs up at ~35 MB/s; I have just selected a folder where I store my "User" data.


In addition I have installed Hyper-V on let the network be managed via Hyper-V.

Another strange thing: As soon as Veeam backs up my E drive I have no longer a stable network connection; even if it has finished.
Windows does not show any warning icon that I have no network connection or something similar but I usually get timeouts when opening a website with Firefox.
Also if I try to reboot the machine it gets stuck at "Rebooting" screen. I need to do a hard shutdown via power button.

From a throughput perspective it should not be a problem: My network runs at 10 Gbit.

Any ideas/suggestions what I might try?

[HannesK]

Hello,
that looks more or less normal for me. As you selected "user data" it is file based backup (vs. block based backup for "operating system").

I did not understand where you are running Hyper-V, but I assume that is is installed on the workstation. And I also assume, that you are running normal applications in the Hyper-V parent partition (the user interface you are working on). All in all a setup that is error prone and I would say "expected"

My suggestion is to "clean" the setup

Best regards,
Hannes

[showiproute]

Hello Hannes,

thanks for your reply.
So the whole backup process is setup as "file based" - why does Veeam process my C drive faster than my E drive?
From my understanding it backs up the C partition, EFI and so on.

Regarding Hyper-V: Yes I run it on my workstation (basically it's a Win10 Pro VM which I use for work).


Beside the process of having a fast and not so fast backup - why does my network have issues as soon as Veeam backs up my E drive (user data) and also after finishing the whole backup process?


Best regards,
Mathias

[showiproute]

Okay so I have change from file based backups to volume based - nevertheless the network connection is not working properly.
Websites open either very slow or not.

Network of my VM is totally frozen. I cannot ping my own LAN IP address (192.168.10.200) while pinging to 127.0.0.1 works.

From my point of view the issue/error is somewhere linked to the Hyper-V managed LAN on my desktop.

[showiproute]

Also if I restart my VM the whole Hyper-V manager on my workstation becomes "Not responding".

[HannesK]

why does Veeam process my C drive faster than my E drive?

block based vs. file based backup. block based is faster

From my point of view the issue/error is somewhere linked to the Hyper-V managed LAN on my desktop.

yep, I also guess that.

[showiproute]

Hi Hannes,

unfortuatnely I cannot quote your quotes
Regarding Hyper-V + "yep, I also guess that."

Are there any known issues when backing up a local computer with a running Hyper-V vm?

In addition are there any known limitation when Hyper-V is managing the NICs/LAN?

[HannesK]

it's a "not supported" setup. So chances are low, that anyone ever tracked such kind of issue. I mean, we create a VSS snapshot on the root partition of Hyper-V. Obviously that's not a great idea

Some background on what Hyper-V is: https://docs.microsoft.com/en-us/virtua ... chitecture - you are working on the root partition. It's not built for that...

There are quote buttons in the full editor

[showiproute]

Some background on what Hyper-V is: https://docs.microsoft.com/en-us/virtua ... chitecture - you are working on the root partition. It's not built for that...

Yesterday it did also not work when my VM was shutdown.
I'll try to remove the Hyper-V management from my NICs.