Bug: Timeout change after upgrade from 12.5 to 15
Replication tasks, which consist of multiple machines or mailboxes fail after upgrade due to a timeout after 12 minutes, if the partial job is still in the queue.
Reason: Timeout values in configuration file are set to 720.
In Acronis Cyber Backup 12.5 this have been minutes - therefor 720 minutes are 12 hours.
In Acronis Cyber Backup 15 this value is handled as seconds, so 720 seconds are 12 minutes.
Still not fixed in the latest upgrade.
Best greetings from Germany
Olaf

- Log in to post comments

Hello Olaf,
thank you for posting on Acronis forums!
Thank you for your attention and cooperation in finding this discrepancy.
Could you please share with us a screenshot showing this Timeout value configuration page?
- Log in to post comments

It's not a page, These timeout values are stored in the file
C:\Program Files\Acronis\BackupManager\backup_manager.yml.
Case ID: 04637591
Best greetings from Germany
Olaf
- Log in to post comments

Hello Olaf,
thank you for sharing these details.
We recommend that you continue the investigation of this issue with the support engineer who works on your case. You will get a response when the information from the affected machine is gathered, analyzed, and tested.
We thank you for your cooperation on this matter.
- Log in to post comments

I always wonder, why the information has to be gathered from "the affected machine" if the issue is reproducable on all systems as soon as I add multiple source locations into one replication job and each of the partial tasks takes more than 12 minutes to complete. So it should be easy for Acronis to perform the reproduction themself.
(It is always time our customers have to pay for without having any benefit.)
Best greetings from Germany
Olaf
- Log in to post comments