The DR wizard with the Sefthy Agent

As soon as the DR is active you land on its page and the setup wizard starts. Four steps in the Console plus the first backup. You do not type the server configuration, the agent detects it and you confirm it.

1. Generate the install command

You generate the command from the page and the token goes inside it. The token expires 24 hours after it is generated.

1. Click Generate the install command.
2. Pick Windows or Linux.
3. Click Copy the command.
4. Paste it on the server in a terminal opened as administrator.

The command downloads the agent, runs it and closes the window on its own when it is done. This is the shape you see, with address and token already filled in.

# Windows, PowerShell as administrator
(New-Object Net.WebClient).DownloadFile('https://static.sefthy.cloud/agent/<version>/sefthy-agent-windows-amd64-legacy.exe', "$env:TEMP\sefthy-agent.exe"); & "$env:TEMP\sefthy-agent.exe" setup --console https://console.sefthy.cloud --token <token>

# Linux, as root or with sudo
curl -fsSL https://static.sefthy.cloud/agent/<version>/sefthy-agent-linux-amd64 -o /tmp/sefthy-agent \
  && chmod +x /tmp/sefthy-agent \
  && sudo /tmp/sefthy-agent setup --console https://console.sefthy.cloud --token <token>

The page waits and moves on by itself as soon as the agent connects.

If the agent does not start, it is almost always the antivirus or the EDR blocking an executable it does not know yet. Click Cannot install it? and you get the file publisher, the SHA-256, the install path, the outbound domains and the ports, ready to hand over to whoever runs security on that server.

2. Verify the data

The agent reports CPU, RAM, disks, UEFI or BIOS firmware and every network card with IP address, netmask, gateway, DNS, VLAN and MAC address.

Check what you see and correct it only if needed. If you change something on the server while you are here, Detect again reads the machine once more. When the data is right, click Confirm and continue.

These are the values the machine restarts with in the cloud. Typed by hand, a wrong address shows up at restore time, which is the worst possible moment.

3. Installation

Now the agent works and the Console follows step by step.

• Configuration detected and saved
• Backup client installed and authenticated
• Device registration on the backup service
• Network drivers, on Windows

Without the network drivers the restored machine has no network. On Linux they are installed automatically at the first backup. If a driver needs a reboot we tell you here, the server is never rebooted for you.

If something stalls, the step does not stay silent and names the reason, for example the backup client logged in to another account or a failed installation, with whatever the machine reported.

4. Connector

The agent looks for the connector on the server network and the Console shows what it found. Three outcomes cover almost every case.

• Connector found and verified. It is already selected in the list below, with the Detected on the network chip. You check it and finish.
• Sefthy device detected, not active yet. Click Activate and associate. The device configures itself, it takes a couple of minutes, and ends up operational and already associated with this DR.
• No connector answered on this server’s network. This can be normal, the connector may sit on another network of the customer. Pick a connector from the list or create a new one. Search again runs the scan once more.

5. Confirm and first backup

Click Complete setup. The wizard closes and you are on the DR page.

From here you set the backup schedule and run the first backup. Until the first backup is done the DR cannot be restored, and the page says so.