How to perform a Cloud Restore with the Connector
How to restore the customer's server in the Sefthy cloud, bridged to their LAN by the connector and reachable at the same local IP address. Starting the restore, picking the snapshot and checking the restored server.
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 the server answers on the same IP address as before, as if it were still on site.
If the whole site is down instead, the connector cannot bridge the server to the network and you need the restore with the Emergency VPN.
Anteprima video temporaneamente non disponibile.
Apri il file direttamente →Starting the restore
- Open the DR page and click Initiate DR.
- Review the Pre-flight checks. They are two rows updated in real time, not a checklist to tick. The first shows whether the Original device is still reachable, the second whether the Connector is online. If either is red, fix the problem before proceeding.
- In the destination selector choose Cloud.
- Click Restore with Connector.
If the DR belongs to a restore group, the top of the window shows the Restore entire group (Orchestrated Disaster Recovery) switch. If you leave it on, the Console opens the connector page to bring the whole group back in the order you defined. Turn it off to restore this server only.
The counter of recovery days included in the plan starts when the virtual machine is created, not when you click the button. The days are 7 for Trial and Mini, 10 for Sefthy and 20 for Sefthy PRO.
Picking the restore point
While Sefthy prepares the restore environment, the band at the top of the page shows Preparing DR. This can take a few minutes and you do not need to stay on the page.
Once the environment is ready, the three-step selector appears.
- Day. On the calendar, days marked with a dot hold at least one snapshot. Click the day you need.
- Snapshot. In the right-hand column pick the exact point in time.
- Disks. All disks are already selected. Untick the ones to exclude from the restored machine, then click Start Recovery.
The band changes to Restoring and the progress bar appears inside the Latest Activities card.
If the selector stays empty
The message “No snapshots found” has three possible causes.
- No backup has ever succeeded. In this case Initiate DR was already grey.
- The server runs Linux and its backups end with a warning. These backups are valid and restorable, but they do not count as successful until support turns on the Warning = Success switch on that DR.
- A storage issue on the Sefthy side, which support resolves.
In the last two cases open a ticket stating 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’s operating system starts. The DR page shows the Restore complete band, with the remaining days counter and the Manage the VM button.
From there open the VM detail and click Console remota to see the server desktop. Log in and check the network card configuration. If the original static IP address is missing, you can set it again from there. 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’s local network as if it were still on site.
When the original hardware is operational again, the return is described in Return on premises after a cloud DR.