Replicatioin fails with end of file error
Today replication failed - not sure why - but it spits out and end of file error. The backup task runs 10 minuters after the PC boots, as you can see from the log file that was early this morning. Several hours later it stops with error message.
25/09/2019 7:37:12:231 AM +10:00 9012 I00000000: -----
25/09/2019 7:37:12:231 AM +10:00 9012 I00000000: ATI Demon started. Version: 24.3.1.20770.
25/09/2019 7:37:12:282 AM +10:00 9012 I00640002: Operation On Boot test 2020beta-replica started by schedule.
25/09/2019 7:37:12:616 AM +10:00 9012 I013C0000: Operation: Replication
25/09/2019 7:37:15:259 AM +10:00 9012 I0064000B: Priority changed to Low.
25/09/2019 11:03:26:327 AM +10:00 9012 E00000000: Replica error: Error 0x40002: The end of the file has been reached.
| line: 0x4df5a451c224a597
| file: c:\bs_hudson\workspace\1105\home\backup_worker\impl\process_io.cpp:93
| function: Home::ProcessIoImpl::ReadLineFromStdout
| line: 0x4df5a451c224a597; c:\bs_hudson\workspace\1105\home\backup_worker\impl\process_io.cpp:93; Home::ProcessIoImpl::ReadLineFromStdout
| $module: ti_demon_vs_20770
25/09/2019 11:03:26:328 AM +10:00 9012 E00000000: Can't stop backup worker: Error 0x40003: Error occurred while writing the file.
| line: 0x4df5a451c224a57f
| file: c:\bs_hudson\workspace\1105\home\backup_worker\impl\process_io.cpp:69
| function: Home::ProcessIoImpl::WriteLineToStdin
| line: 0x4df5a451c224a57f; c:\bs_hudson\workspace\1105\home\backup_worker\impl\process_io.cpp:69; Home::ProcessIoImpl::WriteLineToStdin
| $module: ti_demon_vs_20770
25/09/2019 11:03:26:340 AM +10:00 9012 E00040002: Error 0x40002: The end of the file has been reached.
| trace level: error
| line: 0x4df5a451c224a597
| file: c:\bs_hudson\workspace\1105\home\backup_worker\impl\process_io.cpp:93
| function: Home::ProcessIoImpl::ReadLineFromStdout
| line: 0x4df5a451c224a597; c:\bs_hudson\workspace\1105\home\backup_worker\impl\process_io.cpp:93; Home::ProcessIoImpl::ReadLineFromStdout
| $module: ti_demon_vs_20770Start: 25/09/2019 7:37:12 AM
Stop: 25/09/2019 11:03:26 AM
Total Time: 03:26:14
It is possible that the problem was caused by my updating to the latest build when replication had not completed - unfortunately there is no obvious indication when replication is happening. Will see if it works tomorrow.
Ian
Ian,
I would have to repeat Steve's position here. My upload speeds, even though better than his, are not sufficient to be workable for replication. I sure hope that replication comes to local devices soon as I would love to take advantage of it!
I think a old ATI 2020 Build is used ( Version: 24.3.1.20770 ).
@G. Uphoff: Yes, I was using build 20770 when the backup was initiated. I installed the current version after the backup had completed but, I suspect, while replication was still taking place.
I would have thought that the installer file would deal with any active task - my recollection is that it handles backups that are in progress without issue.
I have submitted feedback so hopefully there a solution will be forthcoming.
The failed replication is no longer appearing in the activity TAB. The first screenshot was taken yesterday after the problem was identified and the second a few minutes ago.
Ian
Things are getting very weird. The failed replication message has reappeared, but it is out of order. Indicates some serious coding problems ….
Ian
Ian,
Could be that the installer halted the replication process which resulted in the error then subsequently ran the backup again to completion.
The replication did not restart (at least according to the Activity tab); there was a new replication after then next scheduled backup. It is very odd. Just reviewed and noticed that the replication was of a full backup which takes much longer than for an incremental one, suggesting that it was indeed interrupted by installing the update.
Ian
Ian,
That's what I was meaning to say. Backup halted and re-ran after the install. At least it did pick up and work again.
The whole process with Replica can be a bit confusing. It looks like there are still a few bugs in the associated code as it should have done something cleaner than just stopping the replication to the Cloud without automatically resuming the task.
Just cottoned on the fact that when replication is taking place the dot next to Acronis Cloud is blue rather than green. Must remember that in future.
Ian
IanL-S wrote:The replication did not restart (at least according to the Activity tab); there was a new replication after then next scheduled backup.
I can confirm that the replication task at this point doesn't resume if interrupted. On the next replication start all replicated data will be replicated again. There is a corresponding dev task for the Update 2 to support resumable replication.
Ekaterina, thanks for confirming the behaviour and that it is scheduled to be fixed in Update 2.
Ian