How to perform a Cloud Restore with the Connector

Bring the customer server back to life inside the Sefthy cloud, bridged to their LAN by the connector and reachable at the same local IP as before.

When the protected server goes down, a cloud restore recreates it as a virtual machine in the Sefthy cloud and bridges it to the customer network through the connector. From that moment it answers on the same IP address as before, as if it were still in its rack.

If the whole site is down instead, the connector cannot act as a bridge and the way in is the restore with the Emergency VPN.

From the Initiate DR modal to picking a snapshot

Starting the restore

  1. Open the DR page and click Initiate DR.
  2. Read the Pre-flight checks. They are two live rows, not a static checklist. The first says whether the Original device is still reachable, the second whether the Connector is online. If either is red, fix it before going on.
  3. In the destination selector choose Cloud.
  4. Click Restore with Connector.

If the DR belongs to a restore group, the top of the modal shows the Restore entire group (Orchestrated Disaster Recovery) switch. Leave it on and you are taken to the connector page to bring the whole group back in the order you defined. Turn it off to restore this server only.

From here the recovery days included in the plan start counting, 7 for Trial and Mini, 10 for Sefthy, 20 for Sefthy PRO. The count starts when the virtual machine is created, not when you click.

Picking the restore point

The band at the top of the page turns to Preparing DR while Sefthy sets up the restore environment. It can take a few minutes and you do not need to watch it.

Once ready, the three-step selector appears.

  1. Day. On the calendar, days with a dot hold at least one snapshot. Click the one you need.
  2. Snapshot. In the right-hand column pick the exact point in time.
  3. Disks. They are all selected already. Untick the ones you do not want in the restored machine, then click Start Recovery.

The band turns to Restoring and the progress bar appears inside the Latest Activities card.

If the selector stays empty

“No snapshots found” has three real causes. The first is that no backup ever succeeded, and in that case Initiate DR was grey to begin with. The second concerns Linux servers whose backups close with a warning, valid and restorable but not counted as successful until support turns on the Warning = Success switch on that DR. The third is a storage issue on the Sefthy side, which support sorts out. The last two are fixed with a ticket, quoting the DR name and the date of the last backup you expect to find.

The restored server

When the restore ends the virtual machine reboots and the customer operating system starts. The DR page shows the Restore complete strip, with the remaining days counter and the Manage the VM button.

From there you open the VM detail and click Console remota to see the server desktop. Log in and check the network card, because if the original static address is missing you can set it again from here. On servers prepared with the Sefthy Agent, the network drivers are already installed and the machine answers straight away.

From this moment the server is reachable from the customer local network as if it were still on site.

When the original hardware is healthy again, the way back is covered in Return on premises after a cloud DR.

In the press