REPLY: 3:640/1384 5c95c6b6   
   MSGID: 2:240/77 5c96208f   
   CHRS: LATIN-1 2   
   TID: hpt/lnx 1.4.0-sta 09-04-05   
   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)   
   SEEN-BY: 15/2 123/1970 226/17 229/107 275 354 426 452 616 1014 240/77   
   SEEN-BY: 240/5138 5832 5853 249/206 317 400 280/464 292/854 310/31   
   SEEN-BY: 317/3 320/219 322/757 342/200 393/68 633/280 2432/390 2452/250   
   SEEN-BY: 2454/119 3828/7   
   PATH: 240/77 5832 229/426