This error indicates that the pre-backup command (which will vary depending on the schedule, but is usually our bare metal backup script or our database backup script) failed or timed out. The default timeout is 12 hours. If the pre-backup command does not finish by then, this usually indicates that something is wrong. To find out why the pre-backup command failed, you will need to look at the appropriate log file(s). These are stored in the same folder as the backup script file (or a sub-folder). To locate the log files:
- Login to eSilo Backup and go to Schedule >> Edit. Select the schedule with the error.
- In the window that opens, go to Advanced Options and copy the full path of the Pre-Backup Command script (example: D:\eSilo\esilo_backup_windows_server.cmd)
- Open a Windows Explorer window and navigate to the parent folder where the script is stored (example: D:\eSilo)
- Here you should see the pre-backup command log files, usually named backup.log
- Right click on any .log file to open it in Notepad, or attach it to an email and send it to us at support@esilo.com
If you need assistance with any of the above, send us an email at support@esilo.com. You can also use a form to contact eSilo Support to have our engineers perform a full user check which should detect and resolve the problem. If you need assistance with any of the above, send us an email at support@esilo.com. You can also use a form to contact eSilo Support to have our engineers perform a full user check which should detect and resolve the problem.
