Search the Community
Showing results for tags 'conflict-resolution'.
Hi, I have a readyNAS running Resilio with identity (nas) and have installed it as a service on my Windows machine with identity (desktop). I'm trying to get my head around the naming and sharing conventions used. I essentially want to backup all files in a selection of given folders on my desktop to the NAS so that in the event of a disk failure on the windows machine the files will be on the NAS. When I add files they should ideally be synced to the NAS either on a schedule or immediately. I want to ensure that all files are completely backed up to the NAS at all times. It's unclear to me from the documentation how I can do that. Do I need to share the same identity across the both installations? Seems weird having a windows installation with identity (nas). Also in this scenario I assume that if I edit or delete a file on the readyNAS from some other connection that those changes will propagate to my windows desktop. Does that happen automatically and if not how does the subsequent conflict get handled if I was to also edit the file in windows before the NAS synced up to it?
Hi, Let's say I've got three storage nodes A,B and C. The process 'updateLog' which runs on each of the nodes regularly updates the content of a STATUS.LOG file. Let's say I set up BitTorrent to synch this file between A,B,C. Assuming that time is synchronized between the nodes, one should expect that all nodes at any given time contains the most recent file (timestamp-wise). 1) What happens if A updates STATUS.LOG, but can't get in touch with B and C? Will A simply attempt to retry synchronization until it gets in touch with B and C again? 2) What happens if A updates STATUS.LOG at the same time as B updates the STATUS.LOG - but A can't get in touch with B or C? Will A, when it again can establish contact with B and C, simply realise that it holds a stale version of STATUS.LOG and instead apply the version which B holds? Thanks!