Hello,
Recently we started testing Veeam replication and saw weird issue on the destination NSX-T environment. When replication job runs it creates a new port for the replicated VM on the destination NSX-T LS and leaves old ports attachments as leftovers.
So, for example, if we run the job 2 times we end up with 3 ports on NSX-T LS - 2 leftovers ( VIF attachment ) and 1 actual working port ( VM attachment ).
The replication job is a standard replication that users snapshots ( not CDP ) with network mapping between source and destination NSX-T LS.
-
- Lurker
- Posts: 1
- Liked: never
- Joined: Mar 25, 2021 3:33 pm
- Full Name: Filip Hristovski
- Contact:
-
- VP, Product Management
- Posts: 7081
- Liked: 1511 times
- Joined: May 04, 2011 8:36 am
- Full Name: Andreas Neufert
- Location: Germany
- Contact:
Re: ID: #01798514: Veeam leaves leftover ports on NSX-T LS
Let´s have our support team have a look.
-
- VP, Product Management
- Posts: 7081
- Liked: 1511 times
- Joined: May 04, 2011 8:36 am
- Full Name: Andreas Neufert
- Location: Germany
- Contact:
Re: ID: #01798514: Veeam leaves leftover ports on NSX-T LS
I got some internal information about this and forwarded them to our support team. They need to verify based on logs if it matches the sitaution and can comment then.
Who is online
Users browsing this forum: No registered users and 30 guests