# Backup only when host is reachable; retry backup that was missed due to connection issues

**URL:** <https://forum.duplicati.com/t/backup-only-when-host-is-reachable-retry-backup-that-was-missed-due-to-connection-issues/721>\
**Category:** Features\
**Created:** [September 19, 2017, 12:59pm UTC](https://forum.duplicati.com/t/backup-only-when-host-is-reachable-retry-backup-that-was-missed-due-to-connection-issues/721 "2017-09-19T12:59:54Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![DennisDD](https://forum.duplicati.com/letter_avatar_proxy/v4/letter/d/c37758/32.png) [@DennisDD](https://forum.duplicati.com/u/DennisDD)\
**Post date:** [September 19, 2017, 3:43pm UTC](https://forum.duplicati.com/t/backup-only-when-host-is-reachable-retry-backup-that-was-missed-due-to-connection-issues/721/3 "2017-09-19T15:43:39Z")

</div>

exactly. I was thinking of handling this in pre-run and post-run scripts as a workaround: Configure backup job to run very frequently (every 30 minutes or every hour). Then with a pre-run script, check connectivity and see if a run was completed today. In case no connectivity or in case a job was already completed today, return non-zero to abort the job. On every successful run, the post-run could create a file that the pre-run checks for existence.

Too bad these kind of scripts depend on the platform.

---

_[View the full topic](https://forum.duplicati.com/t/backup-only-when-host-is-reachable-retry-backup-that-was-missed-due-to-connection-issues/721)._