| Article: |
Automated Backups with Existing Tools | |
| Subject: | Why Not Ditto? | |
| Date: | 2004-02-10 22:03:01 | |
| From: | datasetgo | |
|
I just posted a brief how-to for backups using ditto rather than ASR and hdiutil. From what I understand, CarbonCopyCloner uses ditto for its backup routines. Plus, it's a one-line script - much easier to implement.
|
||
Showing messages 1 through 4 of 4.
-
Why Not Ditto?
2004-02-11 08:27:24 sharumpe [Reply | View]
-
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?
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




Mr. Sharumpe