Subj : mirdir utility
To   : Paul Quinn
From : Kai Richter
Date : Sat Mar 23 2019 12:36:02

Hello Paul!

23 Mar 19, Paul Quinn wrote to Kai Richter:

 KR>> There is no need to wait until you have collected 1 TB of data. I
 KR>> would just like to know if your tool does copy all files of the
 KR>> mirror or only new or changed ones.

 PQ> There is an option to 'turn off' such checking, so the obverse may be
 PQ> assumed.

Fine. So it does not have an impact of useless writing to your drives that 
would have traffic wear for nothing.

 PQ>   Why don't you check it out, from Sourceforge?

I found my working solution already, too.

PQ> All I use mirdir for is weekly backups of current contents of my local
PQ> & LAN servers.  There a number of generations & levels of backups
PQ> (some daily, some weeklies) wrapped up.

I use rsnapshot for that. rsnapshot is highly configurable for my needs of 
scheduled backups and it does use maintained tools like cron and rsync for 
that. It supports hardlinks on the destination (if supported by the dest. file 
system) so any new backup will contain all files but the backup will grow with 
the size of the changed/new files only. With rsync similar will work on file 
level for traffic and disk wear. Only those parts of a file that have been 
changed would be transfered and written to disk. Very useful for msgbase files 
which remain the same except new content at the end.

Regards

Kai

--- GoldED+/LNX 1.1.4.7
 * Origin:  Monobox  (2:240/77)

.