Host-based backup of Microsoft Hyper-V VMs.
Post Reply
ainder
Lurker
Posts: 1
Liked: never
Joined: Nov 11, 2022 5:45 pm
Full Name: Anish
Contact:

Veeam Replication failing between S2D Cluster 2019 and 2022

Post by ainder »

Hi all,

We want to replicate some VMS from a S2D cluster with (Win 2019) to another S2D cluster with (Win 2022) using Veeam.

We now have the strange behavior that VMs cannot be replicated, if the VM is not running on the same host as the CSV Owner where the Disks are located.

I have attached a picture to illustrate that.

Green arrow works and Red arrow doesn't work.
If I move VM2 to Node 503 the replication also works for VM2.

We also have a replication job configured, to a S2d Cluster with Windows server 2019. There the replication works always.

Image

PS: I already have a Veeam Case Open: 05710183

Regards Anish

Logs:

"Failed to download disk 'xxx-svr-114_disk_2_D51671AD-XXXX-4CB2-879E-D13BDC88D0F6.avhdx" and

"Failed to download disk 'xxx-svr-114_disk_1_472A4AEC-XXXX-4953-936F-99874E617BAF.avhdx" and

"Failed to download disk 'C:\ClusterStorage\CSV03\Replicas\bf502fdfdfsf2db906077c82107c2(1)\Scsi0-5\xxx-svr-114_disk_7_1283E6E1-C910-4A35-BB

--deleted by moderator--
PetrM
Veeam Software
Posts: 3264
Liked: 528 times
Joined: Aug 28, 2013 8:23 am
Full Name: Petr Makarov
Location: Prague, Czech Republic
Contact:

Re: Veeam Replication failing between S2D Cluster 2019 and 2022

Post by PetrM »

Hi Anish and Welcome to Veeam R&D Forums!

Thanks for sharing the case ID. Let's wait for the reply from our support team, it looks like a networking issue between node 502 and the target host that happens during data transmission. Probably, you could collect network traffic dumps from the affected node and from the repository to get more ideas for analysis. Also, I edited your post because we don't troubleshoot technical problems on the forum and there is no point to paste debug logs snippets.

Thanks!
Post Reply

Who is online

Users browsing this forum: No registered users and 13 guests