![]() It’s this device identifier that has to be passed to the diskutil mount and diskutil unmount commands. Here’s a typical output from running diskutil list: /dev/disk0Ġ: Apple_partition_scheme *500.1 GB disk1įrom this, we see that the backup disk (the one I’ve cleverly named “Backup”) has a device identifier of disk1s10. I have two shell scripts, mount_backup and unmount_backup, that SuperDuper! runs before and after the copy via these settings in its Advanced Options pane:īoth scripts use the diskutil program, both to get the drive identifier for the backup disk and to to mount it. This keeps the disk off my Desktop and and prevents me from inadvertently opening it, reading from it, and-worst of all-writing to it. The backup drive is always plugged in and running, but I prefer to have it unmounted except when the backup is being made. On my office Mac, I have SuperDuper! set up to do a backup automatically every weeknight. When you need to get your computer back up and running, there’s nothing better than booting from an external drive and having your normal working environment there for you. Hard disk failures never happen at a convenient time, and reinstalling the operating system and all your applications can take forever. My experience with hard disk failures has taught me to clone the entire drive instead of just my data. I use SuperDuper! instead of Time Machine because I like the idea of having a complete, bootable clone of my startup drive, and SuperDuper! is probably the easiest way to make such a clone. I don’t think I’ve made any changes since these scripts were first posted, but this seemed like a good time to bring them all together in a single article. You may have heard that a new version of SuperDuper! was released yesterday, so I thought I’d repost my SuperDuper! scripts. Next post Previous post SuperDuper! scripts redux ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |