advertisement

Article:
  Automated Backups with Existing Tools
Subject:   Why Not Ditto?
Date:   2004-02-11 08:27:24
From:   sharumpe
Response to: Why Not Ditto?

The reason is that the intent was to copy to a dynamically created disk image, not to another disk as a whole. You could probably do the same thing using ditto instead of asr, though since ASR is built for cloning drives, whereas ditto is built for copying files (similar but distinct), ASR may offer benefits over ditto. (I don't know that for sure)


Mr. Sharumpe
Full Threads Oldest First

Showing messages 1 through 3 of 3.

  • Why Not Ditto?
    2005-06-27 11:31:21  LHaim [Reply | View]

    I know it's been a long time, but I tried your "ditto -rsrcFork -c -k /path/of/src/dir /path/to/dest/archive/backup.zip" (with appropriate replacements of paths & names)

    Got the following errors:

    ditto: //automount/Servers: Operation not supported
    ditto: //automount/static: Operation not supported
    ditto: //dev/fd/3: Bad file descriptor


    And ended up with a 2.55 GByte .zip file for a 60 GB HD w/41 GB on it.

    Any explanations/help?

    In general, I've had lots of frustration trying (and failing) to do backup on this mac using different tools/approaches.

    Thanks.
    • Why Not Ditto?
      2005-06-28 13:51:11  peterhickman [Reply | View]

      The problem is, I think, that ditto is trying to access external devices. You should give it a go with the -X option set. This will keep it from trying access different devices.
  • Why Not Ditto?
    2004-02-12 11:01:15  ponder [Reply | View]

    Ditto is capable of creating a single archive file. No need to worry about a static-size image and ditto can compress on the fly. You can pipe the results to another application or store them locally. Here's a piece of my own backup script, run from cron:

    ditto -c -z -rsrc $filesystem - | ssh backup@$DUMPHOST dd of=$filename