• mirdir utility

    From Mike Powell@1:2320/105 to PAUL QUINN on Fri Mar 22 18:24:00 2019
    It's akin to Xcopy, with a destructive backup function that enforces a 'mirror'
    from source to target. KISS.

    Sounds like the old mirrordir utility that used to be in the debian repositories until it went unsupported for too long.

    I still use it, but would be interested in something that is similar and
    still in development.

    Mike

    ---
    * SLMR 2.1a * Madness takes its toll. Please have exact change.
    * Origin: capitolcityonline.net * Telnet/SSH:2022/HTTP (1:2320/105)
  • From Paul Quinn@3:640/1384.125 to mark lewis on Sat Mar 23 09:40:57 2019
    Hi! mark,

    On 03/23/2019 01:13 AM, you wrote:

    mirdir first, and have found the logfile(s) most informative.

    do rotation of the logs but they are time stamped in their file names...

    All I use mirdir for is weekly backups of current contents of my local & LAN servers. There a number of generations & levels of backups (some daily, some weeklies) wrapped up. So much so that I never saw the value of maintaining a library of logfiles.

    If I really was obsessive, it would take me a week just browsing logfiles to the omission of any other activities. I don't bother reading them any longer, with the exception of a single disk listing capture file of a single slice of backed-up files that I may refer to up to a dozen times later in the week. :)

    Cheers,
    Paul.

    --- Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
    * Origin: None of you are real; my sysop types all this in. (3:640/1384.125)
  • From Paul Quinn@3:640/1384 to Mike Powell on Sat Mar 23 11:15:27 2019
    Hi! Mike,

    On 22 Mar 19 18:24, you wrote to me:

    Sounds like the old mirrordir utility that used to be in the debian repositories until it went unsupported for too long.
    I still use it, but would be interested in something that is similar
    and still in development.

    The new one might interest you. (I keep thinking that I started using it from a Puppy version, around the start of the 20-teens.) Checkout the Sourceforge site for mirdir and browse the "files", to see if there's a commonality with what you remember.

    Cheers,
    Paul.

    ... Sure when... OINK FLAP. OINK FLAP. Well, I'll be damned...
    --- GoldED+/LNX 1.1.5-b20130515
    * Origin: Quinn's Rock - Live from Paul's Xubuntu desktop! (3:640/1384)
  • From Kai Richter@2:240/77 to Paul Quinn on Fri Mar 22 22:36:46 2019
    Hello Paul!

    22 Mar 19, Paul Quinn wrote to Kai Richter:

    How many data does it transfer to mirror a photo source with 1 TB
    including 200MB new data over an existing mirror target?

    Hold that thought. I'll let you know.

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

    Regards

    Kai

    --- GoldED+/LNX 1.1.4.7
    * Origin: Monobox (2:240/77)
  • From Paul Quinn@3:640/1384 to Kai Richter on Sat Mar 23 15:28:27 2019
    Hi! Kai,

    On 22 Mar 19 22:36, you wrote to me:

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

    There is an option to 'turn off' such checking, so the obverse may be assumed.
    Why don't you check it out, from Sourceforge?

    Cheers,
    Paul.

    ... This tagline vibrates if you rub it the right way.
    --- GoldED+/LNX 1.1.5-b20130515
    * Origin: Quinn's Rock - Live from Paul's Xubuntu desktop! (3:640/1384)
  • From Mike Powell@1:2320/105 to PAUL QUINN on Sat Mar 23 10:59:00 2019
    The new one might interest you. (I keep thinking that I started using it
    from
    a Puppy version, around the start of the 20-teens.) Checkout the Sourceforge site for mirdir and browse the "files", to see if there's a commonality with what you remember.

    I may check it out but, based on what was in another post here later, it
    sounds like it quit getting updated about the same time that mirrordir did, which makes me wonder if it also is no longer supported.

    Mike

    ---
    * SLMR 2.1a * If all appears to go well, you missed something...
    * Origin: capitolcityonline.net * Telnet/SSH:2022/HTTP (1:2320/105)
  • From Kai Richter@2:240/77 to Paul Quinn on Sat Mar 23 12:36:02 2019
    Hello Paul!

    23 Mar 19, Paul Quinn wrote to Kai Richter:

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

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

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

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

    I found my working solution already, too.

    All I use mirdir for is weekly backups of current contents of my local
    & LAN servers. There a number of generations & levels of backups
    (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)
  • From Paul Quinn@3:640/1384 to Kai Richter on Sun Mar 24 15:53:54 2019
    Hi! Kai,

    On 23 Mar 19 12:36, you wrote to me:

    There a number of generations & levels of backups (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

    I tried to keep it simple, by using just 'tar'. The daily images are essentially snapshots of running Fido systems, mostly my own but some are offsite backup dailies for another node. The weeklies, well really only one now, is for my point's Fido config. All of this traffic is pushed around to my non-listed binkD server by cron jobs.

    Gotta go... time for backups...

    Cheers,
    Paul.

    ... I'm one of those bad things that happen to good people.
    --- GoldED+/LNX 1.1.5-b20130515
    * Origin: Quinn's Rock - Live from Paul's Xubuntu desktop! (3:640/1384)