micokeman

Members
 View Profile  See their activity

  • Posts

    6

  • Joined

  • Last visited

 Content Type 

Posts posted by micokeman

  3. Sync To Folder With Pre-Existing Data

    in Sync General Discussion

    Posted

    @micokeman

    Not 100% sure what do you want to achieve... Do you want your backup server never delete files even if they are deleted on master? Or - Do you want your master never delete files that are removed on backup?

     

    The first option is not possible directly in Sync, while the second is working by default for read-only nodes.

    I am desiring the effects of your second option and thank you for confirming that it is working by default. That's what I thought should happen, but I mis-understood GreatMarko's quote of 'Changes (additions/modifications/deletions). It seems that you are calling the receiving machine (the node or peer) a 'read-only' or 'read & write' based on what is does to OTHER machines rather than what it does to itself - and these settings are set on the machine that is sharing the files. Am I correct in this thinking? I find that the explanation here http://help.getsync.com/customer/portal/articles/1627117-guide-to-ui-share-window- explains it the same way.

     

    As a side note, if my understanding is correct, a 'read-only node' could actually be both a read-only node AND a read-write node based on the share's settings of the other machine.

    @micokeman,

    ...and just to supplement RomanZ's response, whilst the first option that RomanZ's indicates isn't directly possible in Sync, there is a related suggestion over in the Feature Requests forum for a "None-Deleting Node" - If this is the particular functionality you're looking for, consider adding your voice to that thread.

    Thanks! I can't say that is what I'm looking for yet, but I'll have a look at that topic.

  5. Sync To Folder With Pre-Existing Data

    in Sync General Discussion

    Posted

    Changes (additions/modifications/deletions) on a read-only node will be ignored and won't propagate back to read-write nodes.

     

    Changes (additions/modifications/deletions) on a read-write node will propagate to read-only nodes.

     

    Therefore, if your folder with pre-existing data is setup as a read-only node, and you sync it with a read-write node that is empty, the files on your read-only node will be deleted (or rather, moved to the archive)

     

     

    Whoa! I must be doing it completly wrong then! I guess I was sharing the folder as read-only so that the shared folder would not  have files delete from the backup server should the backup server not have them yet of have them accidently deleted.

     

    Should this be the settings then?

    Share a folder with read-write permissions from the main server (nodeA) and add that folder to the backup server (nodeB). Then share that exact folder from the backup server (nodeB) with read-only permission and add that folder to the live database (nodeA). If that is not the case, how do I get data to flow from my NodeA to my nodeB and also delete files on the NodeB that shouldn't be there? Side note, I only plan to have two nodes in total.

  6. Sync To Folder With Pre-Existing Data

    in Sync General Discussion

    Posted

    I started copying data to a backup data server using a sync program (80% of the data was already copied) and have since decided to start using BitorrntSync. If I share the master folder (and share it as read only) and link the folder to the 'same folder' (with pre-existing data) on the backup server, will the pre-existing data be deleted if it is not found on the 'master' data server? If so, how can I make sure it is not 'archived' as mentioned in other posts. I need the space! :)

     

    The goal is to have the backup database be an exeact clone of the 'master' database, even if there are files already on the backup database.