Just one more thing that may make you think about it twice.
The use of -S in rsync is useful as it makes the sync work when you get
stuck. But the fact that you have the sparse file to deal with to start
with is huge in my tests anyway. Below with the sparse file
# ./fullsync-test
Sat Nov 10 20:09:52 EST 2007
Sat Nov 10 20:40:51 EST 2007
And without:
# ./fullsync-test
Sat Nov 10 22:24:41 EST 2007
Sat Nov 10 22:24:58 EST 2007
Look the the difference in time spend doing it.
That's also one of the pretty big issue I try to explain in my first
post and that make the problem very bad as explain before. I couldn't do
it, or finish it before it was suppose to start again.
Here a simple test results between 30 minutes and 59 seconds to the
second test without the sparse one that is only 17 seconds.
I think that's the biggest punch to why I was trying to find a way
around it.
Now just imagine if you saturate servers resources for that amount of
time instead of 12 seconds.
Best,
Daniel
