How to force a restore task to finish even when encountering multiple errors.
It is possible for network connection issues or other temporary server errors to occur at different stages of the restore process, leading to multiple errors. When the error count exceeds the limit, CubeBackup will automatically stop the ongoing restore process and display a
Failed status. At this point, you will need to start a new restore task from the beginning in order to complete the entire process.
However, there may be cases where you want to continue the restore process despite encountering temporary errors on a small group of files or messages, especially for large restore tasks. In such situations, you can follow the steps below to configure this option:
Finish restore task when encountering multiple errors
- Log (or SSH) into your backup server.
Open the configuration file <installation directory>\etc\config.toml on the backup server using a text editor.
On Windows, the default installation directory is located at C:\Program Files\CubeBackup365.
On Linux, the default installation directory is located at /opt/cubebackup365.
In the [Restore] section and change the value of
true. If your config.toml file doesn't contain a [Restore] section or a
continueOnErrorsline, you will need to create one.
[Restore] continueOnErrors = true ...
Restart the CubeBackup service using the following command.
Please run this command.
sudo /opt/cubebackup365/bin/cbsrv restart
Open a Command Prompt as Administrator, and run this command.
"C:\Program Files\CubeBackup365\bin\cbsrv.exe" restart
Open the Windows PowerShell as Administrator, and run this command.
& "C:\Program Files\CubeBackup365\bin\cbsrv.exe" restart
Please run this command to restart the container.
sudo docker restart <container-name>
Now you can return to the CubeBackup web console and initiate another restore task. This time, CubeBackup will continue and finish the restore process, even if it encounters multiple errors.