I have a rather big DirectAdmin server on which it has become impossible to make backups since it causes so much I/O load that Apache and MySQL start to hang. While this is most probably caused by the underlying SAN infrastructure (it's a VM) I cannot solve it there - Linux just keeps on writing.
Now I suspect there's a very simple solution to this problem - if DirectAdmin backup tasks would launch their tar commands with "ionice -C3" or even C2 this problem shouldn't occur, backups just take longer to prepare but who cares. Alternatively it would also be possible to just nice the tar processes themselves away since default I/O priority is derived from CPU niceness - just not sure if this would have enough of an effect.
ionice class -C3 should have the effect of adding no visible system load, which is kind of the effect that I'm seeking with 24/7 loaded DA servers.
My main question: how would I go about testing my theories, which DA scripts should I modify?
Secondary question: shouldn't this be a feature of DA, most probably even enabled by default since backups should never hamper the server's main task of 'webserving'?
Now I suspect there's a very simple solution to this problem - if DirectAdmin backup tasks would launch their tar commands with "ionice -C3" or even C2 this problem shouldn't occur, backups just take longer to prepare but who cares. Alternatively it would also be possible to just nice the tar processes themselves away since default I/O priority is derived from CPU niceness - just not sure if this would have enough of an effect.
ionice class -C3 should have the effect of adding no visible system load, which is kind of the effect that I'm seeking with 24/7 loaded DA servers.
My main question: how would I go about testing my theories, which DA scripts should I modify?
Secondary question: shouldn't this be a feature of DA, most probably even enabled by default since backups should never hamper the server's main task of 'webserving'?