Hi All... I use rsync to backup most of my servers to an offsite co-located server. I've been using this setup for about a month or so now and have been generally pleased with the operation as a whole. But one thing bothers me: I use the following command to actually do the transfers: rsync -ae ssh --stats --delete /source/path offsite.server.name:/destination/ Which then in turn spits out something like this to my log file: ===============================================================rsync[23169] (sender) heap statistics: arena: 17339064 (bytes from sbrk) ordblks: 509 (chunks not in use) smblks: 2 hblks: 2 (chunks from mmap) hblkhd: 1294336 (bytes from mmap) usmblks: 0 fsmblks: 80 uordblks: 17180952 (bytes used) fordblks: 158112 (bytes free) keepcost: 132840 (bytes in releasable chunk) Number of files: 161530 Number of files transferred: 327 Total file size: 97936829135 bytes Total transferred file size: 945709165 bytes Literal data: 741315984 bytes Matched data: 204393181 bytes File list size: 3446549 Total bytes written: 745547229 Total bytes read: 1090478 wrote 745547229 bytes read 1090478 bytes 87035.93 bytes/sec total size is 97936829135 speedup is 131.17 =============================================================== The problem is: I don't know exactly how much it transferred offsite. Can someone please explain the output shown above to me...or point me to a site that can. I've searched Google, the man page, and the documentation and nothing can tell me what this information means. Thanks in advance... -- Kevin L. Collins, MCSE Systems Manager Nesbitt Engineering, Inc.
On Wed, Jun 16, 2004 at 11:16:30AM -0400, Collins, Kevin wrote:> Number of files: 161530 > Number of files transferred: 327 > Total file size: 97936829135 bytes > Total transferred file size: 945709165 bytes > Literal data: 741315984 bytes > Matched data: 204393181 bytes > File list size: 3446549 > Total bytes written: 745547229 > Total bytes read: 1090478 > > wrote 745547229 bytes read 1090478 bytes 87035.93 bytes/sec total size is > 97936829135 speedup is 131.17> The problem is: I don't know exactly how much it transferred offsite.The amount of "Literal data" (741,315,984 bytes) is the file data that we had to send over the socket to the receiver. The "Matched data" (204,393,181 bytes) is the remainder of the file data that was found to already exist in the files we updated. Both of those figures add up to the "Total transferred size" (945,709,165 bytes), which is the total amount of file data in the 327 files that got updated by the transfer. There were 161,530 total files found, and all those files (which includes the ones that got updated) totaled 97,936,829,135 bytes. The "Total bytes written" (745,547,229 bytes) includes the protocol overhead, so if you subtract off the "Literal data" from that you'll discover that there was an overhead of 4,231,245 bytes sent in the same direction as the transfer (the overhead in the opposite direction was 1,090,478 bytes). Keep in mind that if you were pulling the files instead of pushing them that the "Total bytes read" value would be the one that contained the "Literal data" value. ..wayne..
hi, its:> wrote 745547229 bytes read 1090478 bytes745547229+1090478 bytes Regards, Milutin Voinivich Http://www.NasBackup.com/
Thanks Wayne...this is great stuff. Now at least I *think* I understand what's going on. =) Oh, I second the comment from Chris Shoemaker about adding this to the docs. Later all and thanks again. Kevin On Wed, Jun 16, 2004 at 5:02 PM, Wayne Davidson wrote:> On Wed, Jun 16, 2004 at 11:16:30AM -0400, Collins, Kevin wrote: > > Number of files: 161530 > > Number of files transferred: 327 > > Total file size: 97936829135 bytes > > Total transferred file size: 945709165 bytes > > Literal data: 741315984 bytes > > Matched data: 204393181 bytes > > File list size: 3446549 > > Total bytes written: 745547229 > > Total bytes read: 1090478 > > > > wrote 745547229 bytes read 1090478 bytes 87035.93 bytes/sec total > > size is 97936829135 speedup is 131.17 > > > The problem is: I don't know exactly how much it > transferred offsite. > > The amount of "Literal data" (741,315,984 bytes) is the file > data that we had to send over the socket to the receiver. > The "Matched data" (204,393,181 bytes) is the remainder of > the file data that was found to already exist in the files we > updated. Both of those figures add up to the "Total > transferred size" (945,709,165 bytes), which is the total > amount of file data in the 327 files that got updated by the transfer. > > There were 161,530 total files found, and all those files > (which includes the ones that got updated) totaled > 97,936,829,135 bytes. > > The "Total bytes written" (745,547,229 bytes) includes the > protocol overhead, so if you subtract off the "Literal data" > from that you'll discover that there was an overhead of > 4,231,245 bytes sent in the same direction as the transfer > (the overhead in the opposite direction was 1,090,478 bytes). > Keep in mind that if you were pulling the files instead of > pushing them that the "Total bytes read" value would be the > one that contained the "Literal data" value. > > ..wayne.. >