Originally Posted by business_kid
Rsync is for network use (the 'r' bit), and imposes a cpu loading. I gather you are working locally. There are backup programs, and good old tar, cp -a & friends to make this easy. Why 'split the atom' with rsync when you can do it a better way?
From the CPU point of vue, this could probably make sense. Appart from that, the backup "script" wasn't written by myself and I believe that it originally was meant for backing up to a networked drive. But in any case, I believe that rsync is still a good option because of its versatility (local use is documented in the man page) and it's performance with big folders.
cp would imply playing with find and timestamps files, and tar would create archives which doesn't help when you need to get a file back rapidly.
That said, anyone feeling like to discuss this "multibyte character" problem ?