Thanks, With regards to corrupt profiles being ejected from the Group profile or a corrupt profile, I would accept the notion that the code was written to remove these from the list but the profiles once ejected can be reinserted or rebuilt from scratch with the same result. These profiles running outside a group profile work flawlessly, only when they are inserted in a group profile does this occur. I even inserted these profiles in their own group profile then imported them into one group profile and the group profile containing just one profile was removed from the list.
I could also accept group profiles ejecting profiles which communicate to other servers for various reasons, but ejecting profiles which merely move files from folder to folder on the same server leads me to believe the issue lies in the group profile code.
I hope someone can solve this issue as I find the software quite bullet proof (with the exception of the group profile problem) but we rely heavily on grouping profiles for server synchronisation requirements in which group profiles plays a pivotal role. We have been looking at similar software which allows one source to multiple destinations as an alternative but I much prefer Syncback with a rock solid Group profile feature.
All the very best
I could also accept group profiles ejecting profiles which communicate to other servers for various reasons, but ejecting profiles which merely move files from folder to folder on the same server leads me to believe the issue lies in the group profile code.
I hope someone can solve this issue as I find the software quite bullet proof (with the exception of the group profile problem) but we rely heavily on grouping profiles for server synchronisation requirements in which group profiles plays a pivotal role. We have been looking at similar software which allows one source to multiple destinations as an alternative but I much prefer Syncback with a rock solid Group profile feature.
All the very best