Server health and network drift

The signals on the state of the protected server that the Sefthy Agent sends to the Console. Where to read them, what to do when a signal is red and when the machine's network no longer matches the one on record in the DR plan.

The Sefthy Agent installed on the server sends the Console a report on the state of the machine at regular intervals. The report shows whether, if a disaster happened right now, the restore would actually start.

The signals from the server and the network card realignment proposal

What the agent checks

  • Connector visible from the LAN. The agent looks for the connector on the customer network. This differs from the Online indicator, which comes from the cloud through the tunnel.
  • VSS, Windows only. Lists the Volume Shadow Copy writers and flags the ones in error. With a writer in error a backup can succeed and still be inconsistent.
  • Network drivers, Windows only. Checks that the network drivers installed during onboarding are still present. On Linux the drivers are already part of the system and the section does not appear.
  • Disk space. Flags the fixed volumes that are nearly full.
  • System clock. Flags a server clock that is out of sync.
  • Reboot pending, Windows only. A machine waiting for a reboot can lose the freshly installed driver.
  • DNS. Checks that the Console and backup storage addresses resolve.

The agent also detects other backup software installed on the server, the most frequent cause of VSS conflicts. That list is visible to Sefthy support only.

Where you read them

The connector signals appear in the Connector tile of the DR page, under the status indicator. If the server cannot see the connector, the amber line Not visible from the server appears, with a note that the detection can lag by a few minutes. If the agent stops sending its report, Health not up to date appears and the tooltip says since when.

The other signals appear next to failed backups. Open the Latest Tasks card, click the row of the failed backup and under the log you find the block Likely causes from the server, with one line per unhealthy section. The block shows the current state of the server, not its state at the time of the backup.

When a signal is red

  • Connector unreachable from the server. Check that connector and server are on the same network and that no device in between separates them. Until the server sees the connector, a cloud restore through the connector has no link to the LAN.
  • VSS in error. The detail lists the writers in error. Restart the service they belong to, or uninstall the other backup software that uses them.
  • Network drivers not installed. Reinstall the Sefthy Agent from the DR menu. The same procedure also reinstalls the driver. See Reinstalling and updating the Sefthy Agent.
  • Disk almost full. The line shows the free GB out of the total. Free up space before the backup stops.
  • Clock out of sync. Fix the NTP configuration on the server.
  • Reboot pending. Schedule the reboot with the customer and do not put it off for weeks.
  • DNS not resolving. Check the DNS resolvers on the server, which the agent uses to talk to the storage.

Network drift

A restore recreates the network cards on record in the DR plan, not the ones the server has today. If an address changes, a VLAN is moved or a card is replaced without updating the record in the Console, the restored copy starts with the wrong network configuration.

The agent sends the list of the cards actually present. The Console compares it with the record on IP address, netmask, gateway, VLAN and MAC and, when something differs, prepares a realignment proposal without applying it automatically.

On the DR page the amber note The server network has changed. appears with the columns Field, Registered and Detected by the agent, and one row per value that differs. A field never recorded reads not registered, a card the agent no longer detects reads absent on the server. In the DR list the same warning appears as a badge on the DR row.

The note The server network has changed on the DR page, with the value on record and the one detected by the agent

Accepting or rejecting

  1. Read the table and decide whether the detected value is correct.
  2. Click Review and apply. The DR Settings window opens, already filled in with the proposed values and with the changed fields highlighted.
  3. In the same window check CPU and RAM as well, then confirm. The cloud networks of the DR realign automatically.

If the correct configuration is the one on record, click Reject. The proposal is not shown again until the server network changes again, or until you save a new record from the Settings window.

If the note is not there

The proposal only appears while the DR is idle. With a restore in progress, a local restore open or a suspended DR it stays hidden, together with the Settings window that applies it. Seeing it also requires the permission to start a DR.

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.