Reviews:
 ·AT&T Southeast
| Benefits of rsync deamon vs. no daemon I'll preface this with I am rsync noob.
I've been doing research and playing with rync for a project. In the scenario where I need rsync, I will have two Linux servers (opensuse 64-bit) remote to each other. Each day, there can be created some new files that can be anywhere from a few hundred MB to maybe a GB in size. These files need to be synchronized between the servers. The number of files will grow over time and can become quite large (there are 10TB of space on the servers, each). The servers are all in a corporate network, but in different cities. Bandwidth is not expected to be a problem.
So after reading and trying, I am comfortable with invoking rsync with ssh from command line invocations or scripts to perform this work. It works well in the test lab.
In trying to understand why I might or might not want to run rsync in daemon mode, I saw some references to "... when they add caching support to the daemon..." that that might be a performance boost if you have a lot of files that need to be synchronized. I will be having a lot of files, so this was of interest. But I was never able to find out if the daemon mode ever did receive this caching that was alluded to in the info I was reading.
Any advice from the rsync gurus given my description? Would there be a benefit to setting up the daemon in this scenario of lots of large files needing to be synced?
--
nohup rm -fr /& |
|
 DeHackEdBill Ate Tux's Rocket
join:2000-12-07 | In the scenario where the network is adequately trusted I think what it will come down to is performance. SSH authentication and login is great and convenient, but on a fast (gigabit or better) network you're probably going to hit a CPU bottleneck with SSH encryption and a bit of interprocess communication. Rsync in daemon mode will not have this problem.
If this is not an issue to you, then I don't think it makes a difference. There's no cache provided by rsync itself and once invoked there's not a big difference in mode of operation beyond the use of rsyncd.conf.
--
That's odd... |
|
Reviews:
·AT&T Southeast
| Good info. Thank you. I'm not anticipating a cpu bottleneck. Because it is corporate intranet, I suppose I could specify a weaker/faster encryption protocol on the ssh invocations. Not sure the effort is worth the gain.
--
nohup rm -fr /& |
|
