Start a Failover
BetaA failover runs your mission on our platform when your own site is down. It restores the guests, rebuilds your networks, gives public guests their public addresses, and runs until you end it.
Start the failover
Open the mission and click Start failover. First choose the snapshots: the newest ones, or the newest ones before a time. Use the second option after ransomware or data corruption, to bring back the state from before the incident. Unlock encrypted guests, or store their key with the mission as Encrypted backups describes. Then type the name of the mission to confirm.
The guests restore and start in their boot order. A guest that fails does not stop the others, and Retry restores it again.
Make your services reachable
The run page lists the public addresses of the failover: one per public guest, with its published ports, and one Shared address for outbound traffic and WireGuard. Point your DNS records to the addresses of your public guests.
Connect with WireGuard
WireGuard gives you access to every subnet of the failover. Under WireGuard, add a peer for each laptop or office:
Add a peer with a name, for example Admin laptop. We create a key pair and show you a WireGuard config file that holds the new private key.
Download the file at once and import it into the WireGuard app. We do not keep the private key, and the file is not shown again.
Add a peer with a name and select An office with its own WireGuard router. Enter the public key of your router and the networks of your office, for example 10.50.0.0/16.
You get a config file for the router. Put the router's private key where the file says so, and load it on the router. Then your office network reaches every subnet of the failover.
End the failover
When your own site works again, move your data back and switch your DNS records back. Then click End failover and confirm. We delete the guests, the networks and the WireGuard access, and release the public addresses.