Salta al contenuto principale

Script not executed after failed backup

Thread needs solution

The backup task stops and starts a database with pre- and post-exec commands. If the data collection fails (NAS not available, etc.), the post-exec command is not executed and the database down.

Is there an option that the post-exec command is always executed?

0 Users found this helpful

Hello Michael,

I am very much aware of this design problem and this is something we will definitely change in a future, probably with the next update of Acronis Backup 11.5

At the moment, I can offer the following workaround:

- Since this is a database, you will want to use pre/post snapshot commands. This snapshot usually take only a few minutes to finish even for large drives (you can check this time in the product logs for example). With this in mind, you can have the pre script launch a time-delayed command to restart the database something like 5-10 after the pre-command minutes.

In most situations, the post-command will start the DB just fine and the time-delayed command will rerun the start and state something like "database already started". In the rare case where the snapshot fails, the time-delayed command will restart the database with minimal downtime.