Orchestration of DR
How to bring several servers of the same customer back in the right order. Waits, notifications and checks run by the Sefthy Agent on the restored machines.
When a site has several servers, the order in which they restart matters. If the business application starts while the database is still replaying its logs, the application fails and someone has to intervene manually at the most critical moment. With Orchestration of DR you define the restart sequence once and Sefthy runs it automatically.
The feature is included in the Sefthy and Sefthy PRO plans. Configuring it requires the orchestration management permission.
Anteprima video temporaneamente non disponibile.
Apri il file direttamente →Where to configure it
Open the customer’s Connector page. Further down the page is the Orchestration of DR card with the action sequence. Each row is a step. To change the order, drag the handle to the left of the step number.
The Add Action button opens the panel where you choose the action type.
The four action types
- Start VM, restores and starts the virtual machine of the DR selected in Select DR.
- Notification, sends an email with custom text to your company address. Use it to know that a key step has completed.
- Wait, pauses the sequence for the number of seconds you set.
- Check, verifies that the machine just started is ready before moving to the next step.
What a Check can verify
In Check Type you choose the type of check.
- ARP-Ping, checks network reachability. Nothing needs to be installed on the server.
- Agent: service running, the Windows service or systemd unit you name is running.
- Agent: TCP port listening, the port you name accepts connections, for example 1433 for SQL Server.
- Agent: web address responding, the address you give answers with the expected status code and, optionally, with an expected piece of text.
- Agent: path or file present, the file or folder you give exists.
The four checks prefixed with Agent run inside the machine just started and require a Sefthy Agent enrolled on that DR, that is the software you install on the server during onboarding. If the DR has no enrolled agent, saving is refused and only ARP-Ping and the Wait action remain available.
For each check you set How many tries? and the timeout between one try and the next, and you choose whether to receive an email when the check passes and when it fails.
If a check fails
By default the sequence carries on and the check outcome is recorded. This is deliberate. A configuration set six months earlier must not be able to block a customer’s restore.
If stopping is preferable for a given step, turn on If the check fails, would you like to pause the orchestration?. The connector page then shows the pause banner, which states which step stopped and why. Once the problem is fixed, resume the sequence with Resume Orchestration.
Estimated time
Under the sequence the Console shows the Estimated total time to complete recovery orchestration, calculated by adding up the times of the individual steps. It is the figure to give the customer when they ask how long the downtime will last.
Starting the orchestration
The orchestration can be started in two ways, which lead to the same procedure.
- From the Orchestration of DR card on the connector page, with the Initiate DR button. The button appears when every DR in the group has at least one backup and none has been restored yet.
- From the page of a DR that belongs to the group. The Initiate DR window states that the DR belongs to a group and offers the Restore entire group (Orchestrated Disaster Recovery) switch, with the Start Orchestrated Disaster Recovery button that opens the connector page. Turn the switch off to restore that single server only.
In both cases a window opens on the connector page asking how to connect the restored machines, with Restore with Connector or Restore with Emergency VPN. The second option is available only when every DR in the group is on the Sefthy PRO plan. Once you choose, the whole sequence starts.