# Duplicati vs. CrashPlan Home **URL:** \ **Category:** Comparison\ **Created:** [September 8, 2017, 4:55pm UTC](https://forum.duplicati.com/t/duplicati-vs-crashplan-home/515 "2017-09-08T16:55:16Z")\ **Posts on this page:** 1\ **Showing post:** 28
**Author:** ![JonMikelV](https://forum.duplicati.com/letter_avatar_proxy/v4/letter/j/439d5e/32.png) [@JonMikelV](https://forum.duplicati.com/u/JonMikelV)\ **Post date:** [September 19, 2017, 6:06pm UTC](https://forum.duplicati.com/t/duplicati-vs-crashplan-home/515/28 "2017-09-19T18:06:58Z")
I guess it depends on what you mean by “work”. 😃 Maybe you and DennissDD can put your heads together for some scripts like what he described here (at least until official support gets added). > [@Backup only when host is reachable; retry backup that was missed due to connection issues](https://forum.duplicati.com/t/backup-only-when-host-is-reachable-retry-backup-that-was-missed-due-to-connection-issues/721/3): > > 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 p… --- _[View the full topic](https://forum.duplicati.com/t/duplicati-vs-crashplan-home/515)._