Skip to main content

Replication schedule simply stops

Thread needs solution

Some of our customers use Acronis Cyber Backup 12.5 to backup virtual servers to internal storage and then run a replication task with RDX disk as target.

I now experience the 3rd time within the last 8 weeks, that replication simply stopped, just as if someone pressed the deactivate button (which got ignored in the past too, not sure about the latest builds).

Customer 1 had two identical replication jobs with different target drives, one for weekend, one for working days. The weekend job ceased to run, the other job never failed. Changing the time of the execution solved the issue.

Our own company had one daily job stopping around the same time. Plan changes did nothing, but after server reboot for MS updates the task suddenly started to run again.

Now I am stuck on the third customers system, last execution day was 9/11, after that day at least the workday and the weekend replication tasks are no longer executed. No update to latest build, no change of plan and no server reboot had any effect on the behavior in this case.

The scheduler itself seems to be OK, since backup jobs are not affected. The replication jobs work fine, if executed manually. Nasty are the missing red entries and error mails, since the job never makes even an attempt to run, the issue is only seen randomly, if individually checking the media. (In the last case it was my eject script, which delivered a count of 0 tibx files on the media by mail.)

Any ideas how to fix this?

Best greetings from Germany
Olaf

0 Users found this helpful
frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 0
Comments: 2016

Hello Olaf,

thank you for posting on Acronis forums!

There could be various reasons of stopping replication jobs. Each case should be investigated separately.

Customer 1 had two identical replication jobs with different target drives, one for weekend, one for working days. The weekend job ceased to run, the other job never failed. Changing the time of the execution solved the issue.

Please check if the backup location for replication is accessible at the time when replication is performed.

Our own company had one daily job stopping around the same time. Plan changes did nothing, but after server reboot for MS updates the task suddenly started to run again.

Hard to say anything without investigation.

The scheduler itself seems to be OK, since backup jobs are not affected. The replication jobs work fine, if executed manually.

If you run the replication job manually, then it will not be executed at the time of the scheduled start since the required number of e.g. full backups are already at the target location. Please also check the target location accessibility at the scheduled time.