I have a linux box that has a Windows 7 share mounted. The Linux box has a cron job to copy the contents of the Win7 share to another location on the Linux box -- a backup.
The script run is simply
rsync -a etc....
I have another Linux box outside the LAN that runs the same
rsync command between the Linux box in the LAN back to the Linux box outside the LAN -- a second backup.
The problem is that the
rsync command doesn't seem to update files that have changed since the last run of
rsync. I have a file that I know has changed on the Windows box that, on the Linux boxes, is still an old version. I'm wondering if the
rsync command looks at the folder's time stamp and if there is no change, skips the whole directory. Or perhaps something else is going on?
rsync updated files with new timestamps?
EDIT -- to add more details:
The command I run is this:
rsync --ignore-existing --delete --stats --progress -a /hqserver/ /company_data/HQ_Backups/Day
In the LAN there is a Windows 7 machine that holds the company data. User work off of this share from their computers. There is a Linux box in the LAN that uses
samba to mount this same Windows 7 share and
rsyncs the share contents to another location on the Linux box. Then there is another Linux box outside the LAN that runs the same
rsync command to copy the internal Linux box contents to itself.
The cron job runs the command as root. Here's the crontab:
00 2 * * * root python /home/garfonzo/Backup_Scripts/BU_Script.py
BU_Script.py contains the
ls of the folder the backups are sent to:
drwxrwxrwx 9 garfonzo garfonzo 4096 2011-12-03 02:00 HQ_Backups/
Whoa whoa whoa... is the
--ignore-existing flag the root of my problem!?