- TIME MACHINE VS CARBON COPY CLONER FULL
- TIME MACHINE VS CARBON COPY CLONER SOFTWARE
- TIME MACHINE VS CARBON COPY CLONER DOWNLOAD
- TIME MACHINE VS CARBON COPY CLONER MAC
# This script compares the most recent backup to the previous one Just pop it into the (Apple)Script Editor.app and hit the ‘Run’ ▶︎ button.
To make it easier, here’s a handy AppleScript that will do it for you. You can do that in Terminal, too, but the syntax can be a bit tricky. You can find out what got backed up after the task finishes by comparing the most recent snapshot (the one that’s just completed), with the previous one (this is much faster, took about 35 seconds here). Which files did, or did not, get changed, added or removed? On the other hand, you might want to know more about what Time Machine has just done after a backup. Remember that you’re doing a diff on a moving target, so the less you can use the machine for other tasks while this command is running the faster it’ll complete. It could take somewhat longer depending on how much data you’ve got to trawl through. It took about 5 minutes on my mac, but I have a small hard drive. That will compare the machine as it is now against the last backup (See the man page for more options on the output). In particular, if you’d like to see what Time Machine is going to back up just before it’s about to run, execute the following command in the Terminal: If you find Time Machine’s taciturn silence on what it has and will do a bit frustrating at times, the command line utility tmutil can offer you a bit more insight. Disk Inspector’s ‘Set Up’ wizard walks you through 5 simple steps to accomplish all this.
TIME MACHINE VS CARBON COPY CLONER FULL
* after completing Disk Inspector’s set up procedureįor full instructions refer to the Support page, but the basic idea is that on first launch, you run the ‘Set Up’ wizard to configure your tasks in Carbon Copy Cloner. Save all the data to a log file for easy record keeping of your backups See an estimate of the total and available space on each disk (rounded to the nearest GB)Ħ. Open any disk’s root folder in the Finder by double-clicking its name in DI’s main viewĥ. See the OS Version and Build Number on connected, bootable drivesĤ. See the latest backup and (if available) Time Machine backup for the current source diskģ. See dates of all connected disks that have been backed up via CCC*Ģ. Here’s a quick overview of the main features:ġ.
TIME MACHINE VS CARBON COPY CLONER DOWNLOAD
Check out Disk Inspector’s support and download page here:
TIME MACHINE VS CARBON COPY CLONER SOFTWARE
Whatismore, since it’s Christmas :D, I’m publishing this as a free utility on my software site,. Although much of the background work I’ve outlined above is achievable via AppleScript, displaying the data effectively is rather cludgy, even if one uses some of the excellent scripting libraries like Shane Stanley’s ‘Myriad Tables’ to improve on the stock AppleScript offerings.Īccordingly, after about a week or so of wrestling with an acceptable solution, I finally came up with the Disk Inspector.app to solve all these problems in one go and add a few niceties on top. What started out as a simple AppleScripting task soon blossomed into a full-blown app. That’s the outline of the problem and the solution. For example, the connected disk ‘MBP Z Clone’ is a scheduled task on my MBP, but looking at this disk when connected to my iMac gives me no information about its backup history: Since some files are shared or swapped across my three macs, there’s no way to find out from CCC’s Task History or Disk Center when the latest backup of any particular one of those files was made, or on which backup disk I can find it. Further, we don’t need to consider only disk failure as a reason to need comparative backup history. There’s no way for me to see all the backup dates from all my macs with CCC. I have two other macs – two 13″ MacBook Pros that have been going strong since 2009 – each of which I backup to individual clones.
TIME MACHINE VS CARBON COPY CLONER MAC
Thus, if I backup Disk B from Disk C, that information won’t be available to me when I startup my mac with Disk A.īefore I discuss the solution to this, let me just complicate the scenario further.
Third, CCC’s ‘Disk Center’ only provides backup information about connected disks if the current startup disk was used to run the backup task. Second, to compare them, I’d have to boot each clone individually – a time-consuming and not terribly convenient process. First, these cloned task histories do not contain the history from the *last* task (that’s only written to the source disk after the last backup completes). Of course, each backup contains CCC’s earlier History too, but there’s several problems here. Which disk contains my latest backup? The information from CCC’s history task is on the failed internal disk, so it is not now available to me. However, suppose the internal disk fails – just the situation for which I keep my CCC backups on a regular schedule.
0 kommentar(er)
