Application checks after a restore

The four check types the Sefthy Agent runs on the restored machine to verify that the applications respond. How to define them, how to try them on the production server and where the outcomes show up.

The restore test verifies that the machine boots. Knowing whether the ERP also responds takes checks defined by someone who knows the application. That is why you define the application checks, and the Sefthy Agent installed on the server runs them on the restored copy.

Adding an application check and trying it against the production server

Defining the checks

  1. Open the DR page and click the three dots of More actions, at the top right.
  2. Under Configuration click Post-restore validation. Next to the entry you see how many checks are already defined, or not configured in amber.
  3. In the window click Add check and choose one of the four types.
  4. Enter the Check name, fill in the other fields and click Add. The check appears under Defined checks, where you can edit or delete it.

You can define up to ten checks per DR. The Console does not accept an eleventh and asks you to delete one first.

The four types

Path or file. The check verifies that the file or folder exists. On Windows enter a path with a drive letter, for example D:\SQLDATA\acme.mdf, or a UNC path in the form \\server\share. On Linux enter an absolute path, for example /var/lib/mysql/acme/acme.ibd. The Console knows the server operating system and rejects a path with the wrong syntax when you save.

TCP port. The check verifies that the port accepts connections. The Host field is prefilled with localhost and usually needs no change. In Port enter the number, for example 1433 for SQL Server or 5432 for PostgreSQL. Timeout (s) starts at 10 seconds, with a maximum of 30.

Service. The check verifies that the service is running. Enter the Windows service name or the systemd unit name, not the display name. For example MSSQLSERVER and not SQL Server, nginx and not Nginx web server.

Web address. The check verifies that the address responds. In Address enter the URL, for example http://localhost/erp/login, and in Expected status the expected HTTP code, 200 by default. The optional Expected text field holds a string that must appear in the page. Only http and https are allowed and the host must be the protected machine, so localhost, 127.0.0.1 or an IP address on record for this DR. This restriction prevents a check from being used to probe third-party systems.

Trying the checks on the production server

A misconfigured check only comes to light at the next test, which then provides no useful outcome. Try now runs the checks immediately on the production server, with the same engine that will run them on the restored copy.

  1. In the window click Try now.
  2. Checks running on the server… appears. The outcomes can take a few dozen seconds.
  3. Next to each check the outcome appears, passed, failed or not run, with the detail reported by the server and how long it took.

If the server does not respond, No answer from the agent appears. Click Try now again once the server is online. If the server is unreachable when you start the run, the run stays queued and starts as soon as the server is back online. If no agent is installed on the DR, the run does not start and the Console reports it.

A not run outcome is not a failure. It means the check was not executed or that the response could not be read. The Console never counts it as passed.

Where the outcomes show up

Outcomes appear in the automatic restore test report, under the three outcome tiles, with one row and its detail for each check. The outcome of the checks is kept separate from the one on boot and network, so a failed check does not turn a successful restore into a failure. How to read the report is covered in The automatic restore test and its report.

If outcomes arrive for only some of the checks, or do not arrive at all, the report marks them as partial in amber rather than failed. This means the data is missing, not that the outcome is negative.

The same four types are available in the Orchestration of DR as the condition to move to the next step, with the Agent prefix in Check Type. For example, start the database, wait for port 1433 to respond, then start the web server. The full procedure is in Orchestration of DR.

When changes take effect

Changes apply from the next test. When a test starts, the Console freezes the checks as they are at that moment. A check added later does not change earlier reports, and a deleted check stays in the reports already produced. The window reminds you of this at the bottom with Changes apply from the next test.

Need help? Request remote support

In the press

Remote support

Download Sefthy Assist and run it. A Sefthy technician will see your screen and help you.

We answer Monday to Friday, 9 am to 6 pm Italian time. Outside these hours your request stays in the queue and we get back to you.

Only Sefthy technicians can connect, you can end the session whenever you want and nothing stays installed on your computer.

For any question write to us at [email protected].

Sefthy will never ask you to download this program through a call or an email you were not expecting.