Perform multiple backups (non-scheduled)
I have 4 scripts that I run when I perform a backup (1 for each partition I'm backing up, etc.). I'm wondering if there's a way that I can tell SuperDuper to batch run all 4 scripts without having to confirm each one (i.e., exactly as it runs when I schedule the backups). Sometimes you just want to back up everything right away and not have to wait for your regularly scheduled slot. Thanks!
|
You could do it by writing an AppleScript -- are you comfortable with that kind of thing?
|
I'm very much a beginner with AppleScript, but if I was told what to write I could get it going. But I would like to make this a feature request. I used to use Synk for backups and this kind of batch backup was what I used routinely.
|
The easiest way to do this is going to be with a little shell script, actually. Assuming you have these four jobs scheduled, here's all you have to do.
First, open the Terminal application. Then, type: Code:
crontab -l | pbcopy That'll put some stuff on your clipboard. Open Text Edit with a new file, and paste. In there, you'll see a number of lines that look something like this: Code:
30 21 * * 1,2,3,4,5 open file:///Users/dnanian/Library/Application\%20Support/SuperDuper\%21/Scheduled\%20Copies/Smart\%20Update\%20test\%20from\%20Macintosh\%20HD.sdsp/Copy\%20Job.app At the top of the file add, on a line by itself: Code:
#!/bin/sh Finally save the result to your desktop (for now), with an appropriate name (like "BackupNow"). Then, in terminal, enter (each line on its own line, followed by Return, substituting appropriately): Code:
cd ~/Desktop Now, when you double-click that file, it'll automatically queue up all of those backups and they'll run, one after the other. Hope that helps! |
Sorry I haven't replied yet--I've been very busy. But I will give this a shot at the next opportunity and let you know how it goes. And do think about a "batch script" that'd run like a single backup script for future releases (automating all this)--very helpful. Thanks again!
|
Okay, finally got around to this, but I seem to be having a problem. I think the chmod command isn't doing it's thing. Here's what my desktop doc looks like:
Code:
#!/bin/sh Code:
cd ~/Desktop hit RETURN and type: Code:
chmod +x "backupnow.txt" |
Rename the file to "backupnow.sh" in Terminal with:
mv backupnow.txt backupnow.sh That should fix it. |
That didn't do it, but I did a search on Apple Discussions and found this info:
http://discussions.apple.com/thread....77215� I'm don't speaky the Unix, so I don't know chmod a+x from chmod +x, but I think changing to the .command extension did the trick. Thanks for your help. |
a+x says "change user,group and owner to executable", and +x does the same thing. I'm surprised at what Finder did, but I'm glad .command worked.
|
All times are GMT -4. The time now is 07:30 AM. |
Powered by vBulletin® Version 3.8.9
Copyright ©2000 - 2024, vBulletin Solutions, Inc.