Search found 22 matches
- 09 Feb 2023, 23:52
- Forum: Cobian Reflector
- Topic: Fails to autostart on Windows start
- Replies: 5
- Views: 1115
Re: Fails to autostart on Windows start
Despite repairing permissions Reflector does not start with Windows. There's nothing in the log file prior to manual start with administrative privileges. Also it still fails to start unless started as administrator.
- 07 Feb 2023, 22:30
- Forum: Cobian Reflector
- Topic: Fails to autostart on Windows start
- Replies: 5
- Views: 1115
Re: Fails to autostart on Windows start
Just repaired. See what the next restart bring and let you know.
- 06 Feb 2023, 23:24
- Forum: Cobian Reflector
- Topic: Fails to autostart on Windows start
- Replies: 5
- Views: 1115
Fails to autostart on Windows start
Hi I have Reflector 2.3.6 installed as an app with autostart enabled. Despite of this Reflector does not start when I boot Windows. Manual start also fails unless I start it with admin privileges. In Service and application control I find green mark next to the Application auto-starting = Autostart ...
- 07 Nov 2021, 23:57
- Forum: Cobian Reflector
- Topic: Scheduled backup did not trigger
- Replies: 30
- Views: 25182
Re: Scheduled backup did not trigger
For the last few days all tasks triggered just as scheduled. Today I have noticed there's a new version so I updated the Reflector. During uninstallation process there were some errors: The file "C:\Program Files\tools\Cobian Reflector\Cobian.CommonX.CobEncryptX.dll" couldn't be deleted: Odmowa dost...
- 02 Nov 2021, 21:13
- Forum: Cobian Reflector
- Topic: Scheduled backup did not trigger
- Replies: 30
- Views: 25182
Re: Scheduled backup did not trigger
I've uninstalled old version and performed installation of the new .38. I guess it must have been something with the service as now all the backups triggered. I hope they'll fire every time as scheduled.
- 30 Oct 2021, 01:00
- Forum: Cobian Reflector
- Topic: Scheduled backup did not trigger
- Replies: 30
- Views: 25182
Re: Scheduled backup did not trigger
What about those cloned tasks, which I rescheduled a few times, but they didn't fired? Am I missing something here? The most important thing here is reliability. And Reflector still doesn't trigger my backups. I've removed the 624s wait time as previously described and it did not help. Yesterday I ...
- 20 Oct 2021, 20:04
- Forum: Cobian Reflector
- Topic: Scheduled backup did not trigger
- Replies: 30
- Views: 25182
Re: Scheduled backup did not trigger
Yes, the changes need to be "approved" by the engine and send back. But is it ok for Reflector to drop changes, which were in the process of approving, if user modifies another task in meantime? Shouldn't user been informed to hold with any further modifications or even blocked until previous ones ...
- 19 Oct 2021, 23:50
- Forum: Cobian Reflector
- Topic: Scheduled backup did not trigger
- Replies: 30
- Views: 25182
Re: Scheduled backup did not trigger
On the 14th Reflector noticed backups of original tasks, which were scheduled to Monday the 11th, were missed and triggered all of them. Later I've cloned original tasks and removed the 624 second wait time from the first clone's pre-backup events. After several attempts I've eventually managed to c...
- 14 Oct 2021, 12:42
- Forum: Cobian Reflector
- Topic: Scheduled backup did not trigger
- Replies: 30
- Views: 25182
Re: Scheduled backup did not trigger
Would it be ok just to decrease those 10m to 10 seconds in the task I already have? Or you prefer I clone those tasks and change the value in the cloned one?
If the delay is indeed causing the issue, than I assume it is safe to reschedule the tasks for today (to not to wait for Monday), isn't it?
If the delay is indeed causing the issue, than I assume it is safe to reschedule the tasks for today (to not to wait for Monday), isn't it?
- 14 Oct 2021, 09:33
- Forum: Cobian Reflector
- Topic: Scheduled backup did not trigger
- Replies: 30
- Views: 25182
Re: Scheduled backup did not trigger
The reason is to give HDD time to perform Short DST before backup. DST is required because I have disabled the drive's internal background media scan. During BGMS drive checks health of its surface. The data is later used for SMART. Once it is disabled I need to take care for it manually. Short DST ...