Multiple network cards and VLANs in the DR
How to declare several interfaces and several VLANs on a protected server, what Sefthy builds in the cloud and what the connector has to do.
A protected server can have several network cards, including cards on different VLANs. Sefthy recreates all of them on the restored machine, with the same addresses and on the same VLANs, provided they are declared on the DR.
Where the cards are declared
The cards are declared in the DR setup wizard, in the Network cards section.
With the Sefthy Agent the fields are already filled in. The agent reads every interface on the server and reports its IP address, netmask, gateway, DNS, VLAN and MAC address. At the Verify the detected data step you review the values and confirm.
If you fill in the fields by hand, each card takes four values plus the VLAN.
- IP Address and Netmask of the card.
- Gateway, on the first card only, the one tagged primary.
- DNS.
- VLAN, a number between 1 and 4094. An empty field counts as VLAN 1, that is untagged traffic.
Add network card adds a card, the bin icon removes it. The order matters. The first card is the primary one, used by the restored machine for outbound traffic.

One cloud extension per VLAN
Starting from the declared cards, Sefthy extends the site network towards the cloud. One extension is created per distinct VLAN, not per card.
A DR with three cards on VLAN 10, VLAN 10 and VLAN 20 uses two extensions, not three. A DR with two untagged cards uses a single one, because untagged traffic is treated as VLAN 1, on a par with the other VLANs. If two DRs on the same connector both have a card on VLAN 10, that VLAN travels inside the same extension, because it is the same network of the same customer.
When you start the DR, the machine created in the cloud gets one card for every declared card, in the same order and with the matching VLAN tag. The rest of the cloud network configuration is prepared at that moment and removed when the machine is destroyed.
What changes on the connector
There is nothing for you to configure on the connector. The connector receives the map of VLANs to carry from the Console and configures itself automatically.
What must be correct is the configuration of the surrounding network. The switch port must remain a trunk. If you change the interface used for the Cloud Extension, configure the new port the same way, as described in Change the network interface used for the Cloud Extension.
Changing the cards after setup
On the DR page open the More actions menu, the three-dot icon, and choose Settings. From there you can add a card, correct an address or change a VLAN, then save. On save the cloud extensions are realigned automatically to the new VLANs.
Changes are only possible while the DR is stopped. While a restore is running the entry does not appear, because those values are the ones the machine was started with. The settings window is described in detail in DR settings after setup.
When the VLAN changes on the server
If the server is moved to another VLAN, or a card is added or removed, the agent detects the change and the DR page shows The server network has changed.
Review and apply shows a field-by-field comparison between the value on record and the detected one, with the cards marked as changed, new or removed on the server. When you confirm, the record is updated together with the cloud extensions. With Reject nothing changes and the change is not proposed again until the server network changes again.
Apply the change as soon as possible. Until the record is updated, a restore would use the old addresses, and a wrong VLAN would only surface at restore time. The full process is described in Server health and network drift.