This chapter applies to the Time Machine pane. When using Time Machine in macOS 10 mode, which automatically activates the pane Time Machine X, please read the previous chapter instead.
TinkerTool System won’t switch the Time Machine mode of operation while it is running. When you swap the destination disk from APFS to HFS+ while TinkerTool System is open, the application will notice this the next time you will be preparing a maintenance operation and shows an error message in this case. You can simply quit and reopen the program to resolve this situation.
The incremental backup strategy mentioned in the introduction only works if Time Machine can be absolutely sure which files have changed between two consecutive backups and which haven’t. If Time Machine cannot confirm that a given file is identical to the one it saw during a previous run, that file will be freshly copied in the next run.
When the identity of your computer changes, for example if you purchased a new one, or if it had components replaced during a repair, Time Machine has to assume that all the files of your computer have changed. This is true even if you have “cloned” or manually copied the files from the old to the new computer. This means that during the next backup, Time Machine will copy all the files again. Only if you use Time Machine itself to perform a full restore operation of the previous data, will Time Machine “know” that it can safely reuse the previous incremental backup.
The same problem arises if you replace a volume of your Mac, but use something other than Time Machine to copy the data back. Replacing a volume can mean
Only if you copy a disk drive or partition physically (i.e., by a copying the raw data blocks, not file by file) and make sure that the operating system where Time Machine is active doesn’t mount both volumes simultaneously, will Time Machine seamlessly continue its incremental operation. In all other cases, Time Machine has to assume that all files on the entire affected volume have changed and therefore must be fully copied again.
TinkerTool System can help here, letting you manually confirm to Time Machine that a computer or a volume should still be considered the same, although its identity changed. This way, the new item will take over the role of the replaced item, and its history in Time Machine can be continued without requiring a full new backup.
If you need to confirm that Time Machine can safely take over a backup set that was created by a different physical computer or by a different operating system installation on the same computer, you can reassign the backup set to your current system. You should only do this in the aforementioned scenario, where all files have indeed be copied to the new system installation by some other means (not under control of Time Machine). Perform the following steps to do this:
TinkerTool System will guide you through all steps of the procedure. You will need to locate the foreign backup set to complete the operation. In case of a local Time Machine disk, this will be the top folder of the backup set. It has the name of the previous computer and is located in the folder Backups.backupdb on the destination disk. When using APFS, the folder is the Time Machine volume itself.
Depending on how Time Machine was configured before inheriting the foreign backup set, you might need to re-enable Time Machine on the Time Machine pane of System Preferences and change the backup destination.
In case the local volumes of the current computer are different from the ones of the previous computer, inheriting the backup set alone won’t be sufficient. You will additionally need to reassign each volume, which is described in the next section.
As outlined in the introduction, there can also be cases where you need to confirm to Time Machine that it can safely take over the history of a volume in the backup, although the identity of the original source volume has changed. You can reassign a volume in the backup (for all snapshots recorded by Time Machine) to match a volume of your current setup. You should only do this in the previously mentioned scenario, i.e. where all files have indeed been copied from the previous volume to the new volume (not under control of Time Machine, so that Time Machine did not “notice” it). Perform the following steps to do this:
Three items need to be specified:
TinkerTool System reassigns that volume for the entire time line recorded in that backup set, i.e. for all snapshots. It does not matter if the previous volume changed its name during the recorded time period. Time Machine identifies the volume correctly tracking its internal history data.
Do not abuse the two maintenance features to manipulate the backup in any other cases that have not been mentioned here. The backup set could become unusable.
To be absolutely sure that the backup copy of a volume for a specific point in time can be read without problems and is fully intact, you can force Time Machine to validate its internal checksums. As of version 10.11 of the operating system, Time Machine protects each file in the backup by computing and recording a checksum for the content of that file. To verify a backup run for a volume, perform the following steps:
The check will need a considerable amount of time. If problems are identified, TinkerTool System will show a table with all issues after the verification has been completed. The table will list the full paths of the files in the backup where a problem was detected. There can be two types of problems, indicated as follows:
Possible reasons for cases where no check is possible could be:
The list of possible reasons depends on the operating system version and may not be complete.
Time Machine does not usually need any maintenance as long as you don’t replace the source or destination disks. You just define which disk volumes should be included in the backup, what destination drive should be used, and switch Time Machine on. However, there can be certain instances where Time Machine may not run as expected – for example if there is a file system problem on one of the source volumes, or if there was a power failure during a Time Machine run. TinkerTool System can help you to detect possible problems with backups by controlling one of the diagnostic features of Time Machine with a few simple clicks.
You can select two different backup sets and compare all their files. This will show the “true,” incremental contents of a Time Machine backup, rather than the simulated view in the Finder or the Time Machine user interface, which always shows the entire effective backup set at a selected point in time. If some part of Time Machine is failing, this will mean that although specific files have been modified, they have not been included in the next incremental backup copy corresponding to the Time Machine snapshot taken immediately after the modification time. For typical Time Machine problems, the updates for an entire folder would be missing, which can be detected easily when comparing the two backups preceding and following the modification of files in that folder.
You can also use this feature to determine which files have changed on your computer at a particular point in time, or to assess how many files with what storage size are typically part of your backups every hour.
Alternatively, it is also possible to compare the current data on your computer (that is, all files which are selected to be handled by Time Machine) with a specific backup session. This feature is helpful to detect implementation errors in Time Machine. You can immediately see whether the data that should be copied has actually been copied. Note that this type of compare operation takes a significant amount of time, because all files on your computer have to be checked.
To start the comparison of two Time Machine backups, perform the following steps:
Depending on the size of your backup and the amount of data differing between the two selected backup sets, the compare operation may need a few seconds or several minutes to complete. The results will be shown in the table.
If you move the mouse cursor over an entry in the column Changes, TinkerTool System will display a short textual explanation, so you don’t need to learn the abbreviations.
If at least one of the volumes selected to be part of the backup uses the modern Apple File System (APFS), Time Machine will automatically enable additional features:
This basically means that an APFS snapshot can be used as a local snapshot of Time Machine. Working with these snapshots doesn’t require access to the actual Time Machine backup volume.
Other parts of macOS can use the APFS snapshot feature as well. The list shown on the tab Local Snapshots considers APFS snapshots created by Time Machine only. If you like to work with the complete list of APFS snapshots, please see the chapter The Pane APFS.
It is under sole discretion of the operating system when to automatically create or to remove APFS snapshots. TinkerTool System gives you additional manual control about these local snapshots, however.
To create a new local snapshot on all APFS volumes that are part of your Time Machine backup, perform the following steps:
Creating the local snapshot should typically require less than one minute.
You can review all snapshots using the table Available local snapshots on the same pane. The available points in time are listed as separate lines. By default, you will see a list for the entire computer. If more than one APFS volume is in use, it can also be interesting to see the list of snapshots on each volume. Note that the sets of available snapshots can be different on each volume because some volumes may have less free storage space, so they will automatically remove snapshots earlier than others. To select between different volumes, use the pop-up button above the table.
To reclaim storage space on a particular volume, select the volume with the pop-up button above the table, then click the button Reclaim storage space…. TinkerTool System will ask you in a dialog sheet how much bytes you like at least to be reclaimed. You can specify a low value (like 1) to make sure that only the smallest possible number of snapshots will be deleted. The operating system will use its standard policies to automatically select the snapshots that should be removed. At the end of the operation, TinkerTool System will show a summary how many local snapshots have been lost and how much storage space has been freed on the volume.
In some cases, Time Machine may decide to postpone the cleaning operation for some time. In this particular situation, TinkerTool System may not indicate that storage space has been freed yet immediately after requesting a reclaim procedure.
In order to free up as much space from a volume immediately, select the volume at Available local snapshots and click the button Delete all from this volume. Time Machine will understand this as urgent request to reclaim the maximum amount of storage space currently in use for local snapshots.
To delete a local snapshot manually, select it in the table and click the button Delete selected snapshot….
As part of its daily routine, Time Machine cleans up backups regularly, if necessary every hour. After a backup session has run, outdated backup snapshots are removed from the backup disk. Sometimes, you may like to remove a specific snapshot manually, e.g. to free some storage space. You must never do this via the macOS Finder. This could damage the Time Machine backup set, and in addition also the Trash feature of the Finder. TinkerTool System offers you a safe way to remove a Time Machine backup for a certain point in time: