- Veeam Support Knowledge Base
- Network mapping does not work for Hyper-V replicas in Veeam Cloud Connect after renaming Hyper-V virtual switch
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 | 10 | 11 | 12 | 12.1 | 12.2 | 12.3 | 12.3.1 | 12.3.2 | 13 | 13.1 |
| Published: | 2020-08-13 |
| Last Modified: | 2024-06-28 |
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
Oops! Something went wrong.
Please, try again later.
This article relates to a known issue documented in the Veeam Cloud Connect User Guide:
After you subscribe a tenant to a Hyper-V hardware plan, you cannot rename the virtual switch in Microsoft Hyper-V infrastructure that is used by VM replicas. If you rename the virtual switch, replication jobs targeted at the cloud host that use the renamed virtual switch will fail.
Challenge
Cause
Solution
Primary 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.
Alternative Solution
Follow these steps to rename the virtual switch of the existing hardware plan in the Veeam Cloud Connect database:
- Install SQL Server Management Studio.
- Connect to the Veeam instance and create a backup of the Veeam database. For details, see https://www.veeam.com/kb1471.
- 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- Replace 'OLD_SWITCH_NAME' and 'NEW_SWITCH_NAME' with the original name and new name of the affected virtual switch and click Execute.
- Run the affected replicated job once.
If this KB article did not resolve your issue or you need further assistance with Veeam software, please create a Veeam Support Case.
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.
