Cancelling a DR in progress
How to stop a restore started by mistake. What gets deleted, what stays active in the cloud and what happens to the backups.
A restore can be started on the wrong DR, or it can turn out that the server was not actually down. As long as the restore has not finished you can cancel it from the DR page, with the Stop DR process button in the action bar at the top.

When the button is available
The button appears in two situations.
- During a cloud restore, from the moment the restore machine is ready and the page asks you to pick the snapshot.
- During a local restore, from the moment the session with the Recovery ISO USB stick is open.
The button disappears when the restore is finished. From then on the cycle is closed with the return on premises.
In the early stage, while the status band shows Preparing DR, the button is not yet available. Wait for the environment to be ready.
Cancelling requires the permission to start a DR, the same one Initiate DR requires. Without it the Console refuses the confirmation.
What happens when you confirm
- Click Stop DR process. The confirmation window opens, with different wording for a cloud restore and a local one.
- Click Confirm.
In a cloud restore the restored virtual machine is powered off and deleted. The DR returns to its previous state and Initiate DR is available again.
In a local restore the session with the USB stick is closed and the code cancelled. On its next connection the ISO goes back to the code screen. To start again you need to generate a new code.
In both cases the temporary registration created for the restore is removed, so the customer’s device count is correct again.
What stays and what does not
The backups and the original server are not modified. Cancelling only acts on the cloud side and on the restore session.
The cloud machine, on the other hand, is deleted along with all the data written to it in the meantime. If someone worked on the machine after the restore, that work is lost. Check this before you confirm. The recovery days counter is tied to the machine too, so it is deleted with it and starts from zero on the next restore.
If the restore had started the Emergency VPN machine, it is not shut down. The VPN machine belongs to the connector rather than to the single restore, and you manage it from the VPN & Access card on the connector page.
Ending a DR test
The DR test has a dedicated button, End DR Test, which deletes the test machine and puts the DR straight back into the protected state. The test still counts towards the month even if you end it after five minutes. The full procedure is described in Disaster Simulation.
If the automatic test is running
While Sefthy runs the automatic restart test, the DR page is blurred and the action bar is not available. In the middle the page shows a notice that an automatic check is in progress and the Stop automatic restore button, which stops the test and makes the DR available again. The interrupted test still appears in the report history, without the data it would have collected. Use the button only if you need the DR at that moment.