Tridgell continued his work with network-attached storage technologies when he joined Quantum Corporation as a Senior Engineer in the Storage Systems Group. His role once again involved developing functionality and efficiency modifications into Samba to enhance Quantum's GuardianOS-powered Snap Server network-attached storage device. One of the features that he added to Samba at this time was support for Microsoft 's Active Directory technology, a new authentication system introduced with Microsoft's Windows 2000 Server product range.
Initially I just used gzip to compress the sql files down, but as dump files inevitably grew, I decided to look into some alternatives, and in this post I'll share the results of my research. As I'm often sending these backups as e-mail attachments, the size of the compressed file is the main thing I care about, but this isn't the only factor in a comparison. Some of the methods of compression use more resources than others in terms of CPU and memory. I'm not too concerned about this as my dumps are only being done by cron once a day, but I've included a measurement of resource use; the time taken in seconds (as measured by the time command).
All of these commands work. What that means is that: logging into the machine via ssh works, copying files to the server works and rsync works. The problem exists when I try to rsync via ssh. One of two possibilities exists. Either there is something wrong with the server, or I missed some fundamental step in configuring ssh on both client computers. It’s more likely the former. Like I said, I had prior experience setting up ssh and it wasn’t that hard the first few times. I started by checking the ssh and rsync versions I was running.