Hi all, we are using Veeam to replicate virtual machines to a DR site, we have two proxies at the production site and two at the DR site.
We are having issues where most disks are transferring using hot add but occasionally will receive "Unable to hot add target disk xyz.vmdk, failing over to network mode... "
I thought I had resolved this by doing a storage vmotion of the affected machines as they required snapshot consolidation when moved to the temporary datastore and did not when moved back however this issue continues and will affect different machines at different times, but it's usually the same one's affected.
Has anyone come across this?
8:32:01 AMUsing source proxy 0.0.0.0 for disk Hard disk 1 [hotadd] 01:04
8:32:01 AMUsing source proxy 0.0.0.0 for disk Hard disk 3 [hotadd] 00:43
8:32:01 AMUsing source proxy 0.0.0.0 for disk Hard disk 2 [hotadd] 01:25
8:32:01 AMUsing source proxy 0.0.0.0 for disk Hard disk 4 [hotadd] 01:04
8:32:01 AMUsing source proxy 0.0.0.0 for disk Hard disk 5 [hotadd] 01:24
8:32:44 AMUsing target proxy 0.0.0.0 for disk Hard disk 3 [hotadd]
8:33:05 AMUsing target proxy 0.0.0.0 for disk Hard disk 1 [hotadd]
8:33:05 AMUsing target proxy 0.0.0.0 for disk Hard disk 4 [hotadd]
8:33:26 AMUsing target proxy 0.0.0.0 for disk Hard disk 5 [hotadd]
8:33:26 AMUsing target proxy 0.0.0.0 for disk Hard disk 2 [hotadd]
8:34:43 AMHard disk 3 (80 GB) 5.5 GB read at 63 MB/s [CBT]01:31
8:35:48 AMHard disk 1 (90 GB) 7.9 GB read at 101 MB/s [CBT]01:25
8:36:27 AMHard disk 5 (50 GB) 0 B read at 0 KB/s [CBT]00:15
9:33:49 AMUnable to hot add target disk Servernamehidden_replica_3-000001.vmdk, failing over to network mode...
9:33:54 AMHard disk 4 (200 GB) 2.3 GB read at 3 MB/s [CBT]12:41
Thanks
We are having issues where most disks are transferring using hot add but occasionally will receive "Unable to hot add target disk xyz.vmdk, failing over to network mode... "
I thought I had resolved this by doing a storage vmotion of the affected machines as they required snapshot consolidation when moved to the temporary datastore and did not when moved back however this issue continues and will affect different machines at different times, but it's usually the same one's affected.
Has anyone come across this?
8:32:01 AMUsing source proxy 0.0.0.0 for disk Hard disk 1 [hotadd] 01:04
8:32:01 AMUsing source proxy 0.0.0.0 for disk Hard disk 3 [hotadd] 00:43
8:32:01 AMUsing source proxy 0.0.0.0 for disk Hard disk 2 [hotadd] 01:25
8:32:01 AMUsing source proxy 0.0.0.0 for disk Hard disk 4 [hotadd] 01:04
8:32:01 AMUsing source proxy 0.0.0.0 for disk Hard disk 5 [hotadd] 01:24
8:32:44 AMUsing target proxy 0.0.0.0 for disk Hard disk 3 [hotadd]
8:33:05 AMUsing target proxy 0.0.0.0 for disk Hard disk 1 [hotadd]
8:33:05 AMUsing target proxy 0.0.0.0 for disk Hard disk 4 [hotadd]
8:33:26 AMUsing target proxy 0.0.0.0 for disk Hard disk 5 [hotadd]
8:33:26 AMUsing target proxy 0.0.0.0 for disk Hard disk 2 [hotadd]
8:34:43 AMHard disk 3 (80 GB) 5.5 GB read at 63 MB/s [CBT]01:31
8:35:48 AMHard disk 1 (90 GB) 7.9 GB read at 101 MB/s [CBT]01:25
8:36:27 AMHard disk 5 (50 GB) 0 B read at 0 KB/s [CBT]00:15
9:33:49 AMUnable to hot add target disk Servernamehidden_replica_3-000001.vmdk, failing over to network mode...
9:33:54 AMHard disk 4 (200 GB) 2.3 GB read at 3 MB/s [CBT]12:41
Thanks
Statistics: Posted by Jimbo81 — Jun 12, 2024 11:48 pm






