Small MySQL database backup interrupts TCP traffic
===

I have a system I'm developing as follows:

-At any one time, three or four clients which are pumping data to the central server over a TCP socket.<br />
-A Windows 7 Pro, 2.4ghz Dual-Core Xeon server with 4gb (soon to be 8gb) of RAM, which houses both an C# ASPX web application that receives the client data, as well as the MySQL database that the data is then put into.<br />
-A mini-PC that stores the database backups, which are done every night. The batch file that I run, which works fine when there's no incoming TCP traffic, is:

>@echo off<br />
>echo Running dump...<br />
>net use z: \\\\BackupComputerName\SharedFolder >c:\debuglog.txt 2>&1<br />
>cd C:\Program Files\MySQL\MySQL Server 5.5\bin<br />
>mysqldump.exe -uroot -pmypassword --result-file="z:\backup.sql" database_name<br />
>echo Done!

Right now, the database dumps are only about 5 megabytes. Even so, I notice that when the Xeon server carries them out while there's incoming TCP traffic, the client TCP sockets are significantly slowed down, if not disconnected entirely. And the database dump doesn't make it successfully to the backup machine. In fact, it started running in the Windows Task Manager at 8:20pm last night, and as of right now (12:21pm), it's still listed as running! (With no backup file generated yet.) I don't think that it's a coincidence that one of my clients died about a minute after the backup task was triggered last night.

Any ideas for how to reconfigure the backup routine and/or system configuration to make this work would be greatly appreciated.
