IDC Logo

Veeam #1 Worldwide in
Data Recovery & Protection in 2H'22

LEARN MORE

Network mapping does not work for Hyper-V replicas in Veeam Cloud Connect after renaming Hyper-V virtual switch

KB ID: 4001
Product: Veeam Backup & Replication
Published: 2020-08-13
Last Modified: 2020-08-17
mailbox
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please try again later.

Challenge

After Veeam Cloud Connect service provider renames a Hyper-V virtual switch used by a hardware plan and updates hardware plan settings, network mapping and replica failover stop working for this hardware plan. Replication jobs do not generate any errors.

Cause

The operation is not supported by the product, see Hyper-V hardware plan limitations.

Solution

Create a new hardware plan with the intended name and subscribe affected tenants to this hardware plan. For details, see the Allocate Replication Resources section in the Veeam Cloud Connect Guide.

Alternatively, follow these steps to rename the virtual switch of the existing hardware plan in the Veeam Cloud Connect database:

  1. Install SQL Server Management Studio.
  2. Connect to the Veeam instance and create a backup of the Veeam database. For details, see https://www.veeam.com/kb1471.
  3. Click the New query button and paste the following script in the text window:
DECLARE @old_switch as varchar(50), @new_switch as varchar(50)
set @old_switch = 'OLD_SWITCH_NAME'
set @new_switch = 'NEW_SWITCH_NAME'
update [dbo].[Backup.Model.HvHardwareQuotaNetworks]
set switchName = @new_switch,
name = REPLACE(name, @old_switch, @new_switch)
where switchName = @old_switch
  1. Replace 'OLD_SWITCH_NAME' and 'NEW_SWITCH_NAME' with the original name and new name of the affected virtual switch and click Execute.
  2. Run the affected replicated job once.
To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please try again later.

You have selected too large block!

Please try select less.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case
By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Start using Veeam:
Download the product
&
Activate the license key
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please try again later.