|
| Keep in mind that any application that writes enormous files to a
Windows network share will experience gradual but steady performance
degredation over time. This is due to a performance bug in the
Windows itself, and has nothing to do with the application that is
writing the data. This can be easily reproduced by writing a simple
app that does nothing but constantly write a continuous stream of data
to a specified file.
The degredation will occur more slowly if the host of the share has
more memory. Also interesting (and important) is the fact that if the
app that is writing the file closes the file and then reopens a new
file, the performance will jump back up to its peak. This fact is
important because it suggests a good workaround for this issue.
If you are backing up huge (100's of GB, or even TB) sized volumes to
network shares, you should configure your backup so that it will split
the backup image into ~50GB pieces. Most backup apps support
splitting the backup image file. This way performance will stay at
reasonable levels.
|
|