Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest
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.
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.
Follow these steps to rename the virtual switch of the existing hardware plan in the Veeam Cloud Connect database:
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
Your feedback has been received and will be reviewed.
Please, try again later.
Please try select less.
This form is only for KB Feedback/Suggestions, if you need help with the software open a support case
Your feedback has been received and will be reviewed.
Please, try again later.