Skip to main content
Solved

VDRO ver 7.1, Failover failing unable to find Distributed Virtual Portgroup.

S
Forum|alt.badge.img+1

VDRO ver 7.1, Failover failing unable to find Distributed Virtual Portgroup. 

We are no longer using DVPG in our environment but instead use logical switches in NSX-T. Building the recovery location shows that the Orchestrator can see the Logical switches but actual failover looks for DVPG instead of using the logical switches as defined in the recovery location.

[Error] The Distributed Virtual Portgroup prod-10.111 was not found on the Datacenter
DCDataCenter.

Network Mapping shows the source network mapped to the target logical switch. 

BackupNetwork (ESDDataCenter) to prod-10.111 (vDS_NSX_Compute)

 

What am I missing here? Why is VDRO looking for DVPG instead of the logical switch? This is causing the VM not to power on and not be connected to the network. 

Thanks again for your ideas.

Best answer by spider32

Finally got something going on this. Support was able to identify that issue was the logical segment label in NSX-T was using the “/” character which was not being handled properly by the Orchestrator. Had this change to use “_” and the failover work properly.

However, the failback is not working. Orchestrator’s message shows that the target volume is read-only mode. Since we are doing storage plan and failover dictates reverse replication as part of it. The target volume is in data protection mode. However, Orchestrator failback process should be able to handle this. I’m waiting again for Veeam support to provide an answer. 

What’s your take on this? Thanks again!

 

View original
Did this topic help you find an answer to your question?

5 comments

coolsport00
Forum|alt.badge.img+20
  • coolsport00
  • Veeam Legend
  • 4133 comments
  • August 26, 2024

Hi @Madi.Cristil @safiya ...I think this question may be best placed in VRO Den?

Shane Williford - Veeam VMCA/VMCE | Veeam Legend | VUG Leader | VCP-DCV | Twitter: @coolsport00
S
Forum|alt.badge.img+1
  • spider32
  • Author
  • Experienced User
  • 78 comments
  • August 27, 2024

I opened up a ticket to support but nobody seems to be jumping on it :-(

Rick Vanover
Forum|alt.badge.img+10
  • Rick Vanover
  • RICKATRON
  • 765 comments
  • August 27, 2024

Hey @spider32 → If you have an open case, you should let that follow its course. If you need it escalated, that is a different ask. 

Twitter @RickVanover | Email: rick.vanover@veeam.com
S
Forum|alt.badge.img+1
  • spider32
  • Author
  • Experienced User
  • 78 comments
  • Answer
  • September 6, 2024

Finally got something going on this. Support was able to identify that issue was the logical segment label in NSX-T was using the “/” character which was not being handled properly by the Orchestrator. Had this change to use “_” and the failover work properly.

However, the failback is not working. Orchestrator’s message shows that the target volume is read-only mode. Since we are doing storage plan and failover dictates reverse replication as part of it. The target volume is in data protection mode. However, Orchestrator failback process should be able to handle this. I’m waiting again for Veeam support to provide an answer. 

What’s your take on this? Thanks again!

 

S
Forum|alt.badge.img+1
  • spider32
  • Author
  • Experienced User
  • 78 comments
  • October 2, 2024

The failback error was actually due to ESXi FW config not set with the VDRO IP address. This issue was not related to the original one ([Error] The Distributed Virtual Portgroup prod-10.111 was not found on the Datacenter)DCDataCenter. 

 

Just saying so as not to confuse anybody. Thanks.

Comment


Terms & Conditions