Got questions? This way!

On Sefthy PRO plans, an Emergency VPN can be configured in case the Customer site is completely offline or compromised.

The VPN is based on Wireguard and allows you to:

• Remotely access one or more DRs associated with a Connector;
• Surf the Internet with a public IP (for both clients and restored devices).

To proceed with the configuration simply go into Connectors and select the desired Connector. From the detail page you can either manually add users or synchronize them with your own LDAP server (e.g. Microsoft's Active Directory).

In the Configuration box it is essential to set the gateway of the Emergency VPN, otherwise it will be impossible to activate the Emergency VPN. The gateway is the IP address/CIDR of your existing Customer site LAN (where the devices are connected).

The disaster simulation feature allows you to simulate the entire disaster recovery process in a controlled and isolated environment so that you can verify the integrity of the data and the correct functioning of the restored VM.

The process is similar to that used for the Disaster Recovery startup procedure.

1. On the DR summary screen, click “Start DR Test”;
2. Choose a snapshot from those taken in the last N days provided for in your plan and confirm the disks;
3. Wait for the recovery to complete and access the VM via our webVNC.

Limitations:

• The simulation lasts a maximum of 3 hours, after which it is automatically deleted.
• For each DR, a maximum of 4 tests can be started within a month.

The process is performed automatically once a month for the Sefthy plan and 4 times a month for the Sefthy Pro plan.

Upon completion, a report is generated that can be viewed on the DR summary page. In the event of a failure, an email notification is also sent.

This advanced feature is included in the Sefthy and Sefthy PRO plans.

Do you manage multiple servers in the same location? With the DR Orchestration feature, you can define an automatic sequence to restart them in the correct order in the event of disaster recovery. For example, you can ensure that the database server is online before starting the application server.

On the Connector summary page, there is a “Orchestration of DR” panel where you can create automatic actions in case of disaster recovery.

You can build your automation by combining the following actions:

• Start VM – Start the virtual machine after it has been restored.
• Notification – Send a notification email with a custom message. This is useful for being notified when a key step has been completed.
• Wait – Pauses the orchestration for a number of seconds that you define. This gives services or machines time to start up completely before moving on to the next step.
• Check – Check if a restored machine is online and reachable via Arp-Ping.

  In case of failure: You can choose to automatically pause the entire orchestration. This allows you to intervene manually before resuming the process.

  Notifications: You can choose to receive a notification email in case of both success and failure of the test.

Sefthy Archive is the backup solution for folders and network shares that complements Disaster Recovery. It is ideal, for example, if you already image your main disk but also want to save data you have on a secondary disk or share.

Please note: Disaster Recovery and Archive plans share the same space.

By accessing the Backup > Archive section of the Sefthy Console, you will find a dedicated item for each of your Disaster Recovery plans.

Within each Archive, the interface is divided into three main areas:

• a summary of the service (space used, maximum available, and expansion option);
• an area to set the resources to be saved;
• the status of the latest events and activities, with the option to customize the schedule.

You can add local folders or network shares, set upload speed limits, and define a custom schedule.

For non-public network folders, you can also specify the necessary login credentials.

 The Monitor feature is used to periodically check the reachability status of the Sefthy-protected device by measuring latency and packet loss percentage.

The operation is quite simple: from the network interface connected on the internal LAN, 4 arping requests are made to the device, which if present will respond with its MAC Address, and from the responses received latency and packet loss are calculated.

Operating in Layer 2, arping allows us to check whether a device is actually connected to the network, regardless of some network/firewall misconfigurations of the device, which might limit the responses to the classic ping.

For each user level, whether partner or end user, it is possible to configure receiving notifications through email or Telegram.

To configure Telegram, start a chat with @sefthy_bot and it will print your Telegram ID to insert.

To configure SMTP Server, insert the parameters needed to send the notifications.

 When at least one between Telegram and Email  is configured, you can click on the Add button in the Alerts/Notifications section and select the type, client (in case your account is Partner), devices and channel through which to receive communications.