Bestsync performance and priority
Posted: Thu May 08, 2014 11:07 pm
When Bestsync is performing a backup of my files accross the network the disk i/o from my RAID 10 volume is extremely heavy causing the system to be very unresponsive sometimes when running other applications.
For example typing things in my Firefox browser becomes very delayed and laggy and sometimes I get beeping from the system when pressing keys as the system is unable to service key presses from the keyboard.
Is there a way to reduce or lower the priority of the copying process in Bestsync somehow?
I am often using volume shadow copy during many of my backup tasks and I am wondering if it is related to this in some way. I found in the "volume shadow copy" tab a list of different VSS-Writers. I have the default options ticked of "shadow copy optimization writer" and "system Writer". I don't know what the other options do so I haven't touched them. Is there something in these options that might help?
I am running Windows 7 64-bit and Bestsync 2010 5.4.36(64Bit).
I don't think this used to be a problem in the past and if I copy files manually over the same network shares I do not see this issue.
Many thanks,
Richard.
For example typing things in my Firefox browser becomes very delayed and laggy and sometimes I get beeping from the system when pressing keys as the system is unable to service key presses from the keyboard.
Is there a way to reduce or lower the priority of the copying process in Bestsync somehow?
I am often using volume shadow copy during many of my backup tasks and I am wondering if it is related to this in some way. I found in the "volume shadow copy" tab a list of different VSS-Writers. I have the default options ticked of "shadow copy optimization writer" and "system Writer". I don't know what the other options do so I haven't touched them. Is there something in these options that might help?
I am running Windows 7 64-bit and Bestsync 2010 5.4.36(64Bit).
I don't think this used to be a problem in the past and if I copy files manually over the same network shares I do not see this issue.
Many thanks,
Richard.