You want to use Rsync, glad you find that out.
Here are some links to help you determine how you want to implement Rsync in your situation (SSH secured, openly rsync)
Here's a script I'm pretty proud of. It relies on you exchanging a key with the source server (see SSH articles above). Then you invoke this script on a cron'd schedule.
Adjust directories to suit your needs.
What is particularly key about this invocation of rsync is that it is going to preserve the source file tree (folder hierarchy) when it writes into the current directory (the "." at the end of the line). It deletes on the destination those files/folders that no longer appear on the source. In short, it perfectly duplicates files and folders. I DID NOT pay a great deal of attention to file timestamps nor permissions retention, I'll leave that to you..... I have logging enabled for my own reasons, mainly to keep cron happy.
The first time you run this will take the most time. Afterwards, it should quickly slip into "incremental" maintenance of the sync and you should't have a great deal of time spent making the sync.
====filename: backup_web.example.com.sh===============
#!/bin/sh
HOSTNAME="web.example.com"
cd /var/backup/$HOSTNAME
WORKLOG="/var/log/backup.work.log"
ERRLOG="/var/log/backup.err.log"
echo $0 >> $WORKLOG
date 1>> $WORKLOG
echo $0 >> $ERRLOG
date 1>> $ERRLOG
rsync -Rtav --rsh=ssh --delete root@$HOSTNAME:/usr/local/apache/htdocs . 1>>$WORKLOG 2>>$ERRLOG
================================================
"Surfinbox Shares" - A fundraising program that builds revenue from dialup Internet users.