NASLite Network Attached Storage

Well, I finally dug through all the manuals, options and switches and made my commandline strings for rsync successfully, and this seems to promise good performance. (Thanks for your help Eden!)

A couple of questions now remain, where I am stuck:
1) How do I now BATCH three backup "jobs", so that the next one starts after the first is done? (I am using WinXP and the cygwin dll)
(Unfortunately, I am unfamiliar with pearl or similar, so if somebody has some hints for a basic *.bat script, that be great)

2) How do I output a legible log to a file, so I know where there may have been errors?
I tried appending >>C:\rsync-log\rsync-transfer.htm 2>>C:\rsync-log\rsync-error.htm to the rsync commandline string. This works, but the output is not very structured.
Including the switch --log-format=%n%0"-- "%0"-- "%o%0"--"f%0"<br />" did not really bring a much more legible result of the copy/ delete transactions performed either.
Can anyone help? I am envisioning something like:
Source path/source file -- operation: copied -- Target path/target file - success/ fail linebreak

Tony, could it be, that the actual output of the log is dependent of the server side conf file, i.e. not configurable from the client end on WinXP?

TIA,

Hm,

I prefer that logging be done on the client, however, if necessary, we may take a look at exporting an server-side rsync log in the Status pages at a future date...

Use rsync -W which forces whole file mode. This means that if a file is changed it will not use incremental mode and transfer the entire file at expense of bandwidth.

I use rsync every night over Gigabit although it would equal the NAS2 client NAS1 Server scenario. And that pushes ~400mbit. But it's limited by SSH. connections through the rsyncd from that host to the other is a whopping 65MB/sec though.

This is is the command I use on NAS2 on the nightly sync.

If I understood other resources correctly, the logging actually primarily is configured at the server, in the .conf file.
http://lists.samba.org/archive/rsync/2005-June/012845.html says: "See the rsyncd.conf manpage for how to make the daemon log to a file. No other log-file output is directly supported (e.g. for a remote-shell transfer), but you can use the --log-format option and redirect (or tee) the output to a file."

The rsync manual states http://rsync.samba.org/ftp/rsync/rsync.html:

So I am a bit confused at this stage how to actually format and output a log of the transactions.

Reading up on this led me to believe that primarily the server is doing the logging but I can't seem to manipulate the format, nor do I know, where the logging is stored, and how/ where I can possibly access it in the case of NASLite. That's why it seemed to make sense to me to pursue the client side logging.

(http://rsync.samba.org/ftp/rsync/rsyncd.conf.html has the log format options listed.)