You imply in your reply that SyncBack is not able to monitor profiles running as scheduled task, this would appear to conflict with the release notes.
In my case I have SyncBack set to ‘Start with Windows’ to run various periodical background profiles and some profiles that are set to run on changes/on insert. I also have a couple of scheduled tasks to ensure a particular profile runs at a set time (see below).
What appears to have happen is that another instance of SyncBack was started by the task scheduler to run a scheduled profile (as expected), however for some reason this instance of SyncBack did not exit and just sat idle doing nothing (I had two SyncBack icons in the notification area of the taskbar). The next time a periodically scheduled profile was due to run it appears that both instances of SyncBack, the one set to run in the background and this orphaned copy, tried to run this profile and this ‘Unknown Error’ status was generated.
I been involved it the IT industry for many years and have on more than one occasion have come across people that have found that their backups where not as good as they thought, so I admit that I am bit paranoid about backup and backup software therefore when backup software reports unknown errors I find it very concerning.
Andrew.
PS. The only reason I have scheduled profiles set up is so that I can ensure that a profile runs at the right time to ensure that the condition to force a fast backup rescan passes. If the fast backup data contained a timestamp when the last rescan was done and allow you to configure a new rescan after configurable period of time, then my need for scheduled tasks would go away.
- IPC to allow profiles to be monitored and stopped from other processes
In my case I have SyncBack set to ‘Start with Windows’ to run various periodical background profiles and some profiles that are set to run on changes/on insert. I also have a couple of scheduled tasks to ensure a particular profile runs at a set time (see below).
What appears to have happen is that another instance of SyncBack was started by the task scheduler to run a scheduled profile (as expected), however for some reason this instance of SyncBack did not exit and just sat idle doing nothing (I had two SyncBack icons in the notification area of the taskbar). The next time a periodically scheduled profile was due to run it appears that both instances of SyncBack, the one set to run in the background and this orphaned copy, tried to run this profile and this ‘Unknown Error’ status was generated.
I been involved it the IT industry for many years and have on more than one occasion have come across people that have found that their backups where not as good as they thought, so I admit that I am bit paranoid about backup and backup software therefore when backup software reports unknown errors I find it very concerning.
Andrew.
PS. The only reason I have scheduled profiles set up is so that I can ensure that a profile runs at the right time to ensure that the condition to force a fast backup rescan passes. If the fast backup data contained a timestamp when the last rescan was done and allow you to configure a new rescan after configurable period of time, then my need for scheduled tasks would go away.