Do interrupted image replications resume or restart?
-
Does FOG resume an interrupted (either server, lan/wan outage, etc) image replication from master host to storage node in the way that an rsync --append-verify job would, or does it start over with whatever file it finds as not matching, or something else?
-
@Malos Hi, not sure that Partclone can do that… (http://www.partclone.org/usage/partclone.restore.php)
-
@ch3i I meant image replication from master node to storage nodes, I’m sorry. Edited OP for clarification
-
@Malos Sorry
I don’t know. -
Should ask the @Developers about this.
-
@Developers, how about it? Does fog replication service resume or restart transfers being made from the master storage node to non-master nodes?
-
@Malos I must have been really under the weather when I escalated to the devs.
I actually know the answer. Currently the way replication works due to a bug in lftp concerning only replacing changed bits (remember that one @tom-elliott? ), If a change or difference is detected between the source file and destination file, the destination file is deleted and the copy is re-started.
