Replica Loosing Data
I have two computers creating a replica of their full backups to the Cloud. There was approximately 280GB of data pushed to the Cloud. My internet connection went down. When I restarted the Replica my data in the Cloud was gone. I deleted one of the computers backup and replica. Started the Replica again after the full backup. This was the computer that had pushed the most data to the Cloud. Has anybody else seen this behavior?
I have not had any internet connection interruptions that have resulted in this happening. It may be that there have been disruptions but I did not notice because the 4G backup came on line sufficiently quickly.
Like Steve I have had problems with cloud backups restarting from the beginning when there has been an interruption but I do not recall it happening with a replica. I did have a problem when I powered down the computer while replication was happening but it did not result in damage or loss of the cloud backup. I suggest, if you have not already done so, that you use in-app feedback to report this issue. Please make sure that you include a link to this discussion and include a system report.
Ian
This is currently the expected behavior, because the replication feature does not resume when interrupted like the backup to Cloud. Upon the next run, replication is starting to upload the data from the very beginning, while backup to Cloud checks for already uploaded data and resumes from where it left off.
Sorry Ekaterina, but this expected behaviour renders replication a non-starter for me as my computer was spending far too much time just uploading replica data over and over due to the volume and slow upload speed which almost guaranteed a disconnection at some point in the process. Even most FTP services support resuming an upload so this is just not useful with this behaviour of starting over from the beginning every time.
Steve Smith wrote:Sorry Ekaterina, but this expected behaviour renders replication a non-starter for me as my computer was spending far too much time just uploading replica data over and over due to the volume and slow upload speed which almost guaranteed a disconnection at some point in the process. Even most FTP services support resuming an upload so this is just not useful with this behaviour of starting over from the beginning every time.
Steve, valid points here, I hope that we'll be able to deliver resumable replication as soon as possible, but that strongly depends on the roadmap..I register all feedback about this limitation to collect more votes.
Definitely needs to be "fixed". Most of the time it is not a big problem for me as I have fast cable internet connection (95Mbps/35Mbps) but it occasionally goes off line and the backup 4G is much slower.
Ian
Yes, this definitely needs to be fixed. I now have to start over for the third time.
Does replication rebackup the data to the cloud or is it simply copying the locally created backup to the cloud? I would expect it to be the latter so that the data is guaranteed to be the same. If so, it should be possible to interrupt and resume the operation. The technology is definitely there. Alternatively, one could just use a better file transfer app to upload.
I don't speak from experience because I like to keep all my data here on terra firma.
It copies the local backup to the cloud (when doing a full backup). I know this as I have a backup on a very noisy LaCie USB HDD - makes typical Seagate clicking noise whenever it is being written to or read from. Not sure how it handles the incremental backup (which is added to the existing *tibx file locally). Probably uses the index to workout what has to be uploaded to the Cloud to move the latest increment to the Cloud.
Oan