![]() (Plus you've disregarded 0-9 & possibly more too -).) You can't simply say A-M, N-Z without knowing how much space they're utilizing & expected growth of each. So you've got to know how much space particular trees are using, plus anticipated new files, & then see if all (half) of that will (still fit) into an 18. So look at your 30, & see how you can logically separate it into 15 & 15. the versioning location), rather than global settings.I'd think that is something you've got to figure out based on your data sets.Īs it is, you're not likely to have much space left on the 2 18's (assuming the 30 is basically full). But, if you really want to invoke two syncs, it seems to make much more sense to combine those two sync jobs into one, using two left-right base location pairs and possibly local filter definitions and sync-settings (e.g. However, RTS could call a *.bat- or *.cmd-file that would invoke two FFS syncs sequentially. I don't know if RTS can directly call two ffs_batch files. It does therefore not sound to be a good idea to have RTS call an ffs_batch-file unrelated to changes it has detected. You likely want to keep the FFS sync(s) called by RTS as small/compact as possible (hence my above suggestion). Or you might have RTS monitor C:\Users\ipconfig\ and define just 5 FFS syncs, combining the first 4 into 1. If you just want to sync the above 8 folders upon changes in their content, you might consider to simply define 8 RTS tasks, each monitoring the respective folder, and define 8 separate FFS syncs one for each of those 8 folders. Monitoring your entire C:-drive and/or D:-drive will (depending on your settings) likely either continuously or never trigger an FFS sync. right base location of one of your FFS syncs, \MP3\* would refer to C:\MP3\* and to Z:\Backup\MP3\*, but e.g. As per your example, with C:\ and Z:\Backup being the left-, resp. This will prevent the potential problem you seem to anticipate.Īll (include and exclude) filter definitions are relative to the root of your left and right base locations and are therefore never allowed to contain drive-letters. Similarly it is probably also simpler/smarter to use non-overlapping versioning locations,Į.g. It is probably simpler/smarter to sync C:\ to e.g. What is a best practise in your oppinion for the scenario described above?Īs syncing both C:\ and D:\ to Z:\Backup creates an overlap of your two syncs on Z:\Backup, Problem is that inside Z:\Versioning (my deletion folder for versioning) i will have a folder ABC having files that came original from C:\.\ABC AND from D:\.\ABC. ![]() > having 2 folder Pairs versioning may become a problem, since i could have a folder ABC on D:\Download while also on C:\Users\ipconfig\Documents. > I recognized that I am not allowed to use drive letters in the filter section? \Users\ipconfig\AppData\Local\Microsoft\Outlook\* I make use of the filter section and put every folder taht should be synced in the include section: ![]() I would like to go for versioning in case of deletion of a file from the sources.Ģ RTS processes, one on C and one on D -> i have two different versioning drives, but also 2 processes of RTS running.ġ RTS process with 2 Folder Pairs: C:\ and D:\ both mapping to Z:\Backup On C:\ and on D:\ i have some directories to become backed up. I have on my win 10 PC a SSD Drive called C:\ and a 2 TB HD called D:\
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |