Time Machine (OS X)

From Infogalactic: the planetary knowledge core
Jump to: navigation, search
Time Machine
64px
300px
Time Machine's Retrieval Interface on OS X 10.10 Yosemite
Developer(s) Apple Inc.
Initial release October 26, 2007; 16 years ago (2007-10-26)
Stable release 1.3 / October 16, 2014; 9 years ago (2014-10-16)[1]
Operating system OS X 10.5 or newer
Type Backup software
License Proprietary
Website www.apple.com/osx/apps/#timemachine

Time Machine is a backup software application distributed with the Apple OS X computer operating system. The software is designed to work with the Time Capsule storage product, as well as other internal and external disk drives. It was introduced in Mac OS X Leopard.

Overview

Time Machine creates incremental backups of files that can be restored at a later date.[2] It allows the user to restore the whole system or specific files from the Recovery HD or the OS X Install DVD. It works within iWork, iLife, and several other compatible programs, making it possible to restore individual objects (e.g. photos, contacts, calendar events) without leaving the application. According to an Apple support statement:

"Time Machine is a backup utility, not an archival utility, it is not intended as offline storage. Time Machine captures the most recent state of your data on your disk. As snapshots age, they are prioritized progressively lower compared to your more recent ones."[3]

For backups to a network drive, Time Machine allows the user to back up Apple Mac computers through Apple's AirPort networking, and supports backing up to certain network attached storage devices or servers, depending on the version of Time Machine. Earlier versions worked with a wide variety of NAS servers, but later versions require the server to support a recent version of Apple's Apple Filing Protocol (AFP), and Time Machine no longer works with servers using the Server Message Block (SMB) protocol typical for Windows servers. Some of the legacy support can be re-enabled by using hand-tuned configuration options, accessed through the Terminal. Apple's Time Capsule acts as a network storage device specifically for Time Machine backups, allowing both wired and wireless backups to the Time Capsule's internal hard drive. Time Machine may alternatively be used with any external or internal volume.

Time Machine saves hourly backups for the past 24 hours, daily backups for the past month, and weekly backups for everything older than a month until the volume runs out of space. At that point, Time Machine deletes the oldest weekly backup.

User interface

Time Machine's user interface when retrieving a file uses Apple's Core Animation API. Upon its launch, Time Machine "floats" the active Finder or application window from the user's desktop to a backdrop depicting the user's blurred desktop wallpaper. Behind the current active window are stacked windows, with each window representing a snapshot of how that folder or application looked on the given date and time in the past. When toggling through the previous snapshots, the stacked windows extend backwards, giving the impression of flying through a "time tunnel." While paging through these "windows from the past," a previous version of the data (or presently deleted data) may be retrieved.

Storage

Time Machine works with:

  • local storage (volumes directly connected to the local machine, and formatted with HFS+)
  • remote storage (network resources shared from other Macs, from Time Capsule or compatible device)

The significant difference is that when using remote storage, Time Machine uses sparse bundles; this acts as an isolation layer, which makes the storage neutral to the actual file system used by the network server, and also allows to replicate the backup from one storage to another.

Sparse bundles are mounted by OS X like any devices, presenting their content as a HFS+ formatted volume, functionally similar to a local storage.

Operation

Time Machine creates a folder on the designated Time Machine volume (local or inside a remote sparsebundle) into which it copies the directory tree of all locally attached disk drives, except for files and directories that the user has specified to omit, including the Time Machine volume itself. Every hour thereafter, it creates a new subordinate folder and copies only files that have changed since the last backup and creates hard links to files that already exist on the backup drive. A user can browse the directory hierarchy of these copies as if browsing the primary disk.[4]

Some other backup utilities save deltas for file changes, much like version control systems. Such an approach permits more frequent backups of minor changes, but can often complicate the interaction with the backup volume. By contrast, it is possible to manually browse a Time Machine backup volume without using the Time Machine interface; the use of hard links presents each backup to the user as a complete disk copy.

Time Machine appears to create multiple hard links to unmodified directories. Multiple linking of directories is different from conventional UNIX operating systems. As a result, tools like rsync cannot be used to replicate a Time Machine volume; replication can only reliably be done by imaging the entire filesystem.

Apple system events record when each directory is modified on the hard drive. This means that instead of examining every file's modification date when it is activated, Time Machine only needs to scan the directories that changed for files to copy (the remainder being hard-linked). This differs from the approach taken by similar backup utilities rsync and FlyBack, which examine modification dates of all files during backup.

Time Machine is also available in the Leopard, Snow Leopard, and Lion installation process. One of the features in the Migration Assistant interface is to re-install the contents of a Time Machine backup. In other words, a hard drive can be restored from a Time Machine backup in the event of a catastrophic crash.

OS X Mountain Lion introduced the ability to use multiple volumes simultaneously for Time Machine operations. When the user specifies more than one volume to use, OS X rotates among the desired volumes each time it does a backup. [5]

Coding differences between OS X Mountain Lion and Mavericks have resulted in compatibility issues related to Time Machine's system restoration functionality. Time Machine backups created by Apple computers purchased as recently as late 2012 cannot be used for system restoration on 2013 or 2014 models.[citation needed]. However, the data from the backup can still be recovered by directly accessing the files from the Time Machine Volume.

Requirements

Time Machine places strict requirements on the backup storage medium. The only officially supported configurations are:

  • A hard drive or partition connected directly to the computer, either internally or by a bus like USB or FireWire, and formatted as journaled HFS+.[6]
  • A folder on a journaled HFS+ file system shared by another Mac on the same network running at least Leopard.[7]
  • A drive shared by an Apple Time Capsule on the same network.

On a Time Capsule, the backup data is stored in an HFS+ disk image and accessed via Apple Filing Protocol. Although it is not officially supported, users and manufacturers have configured Linux servers and network-attached storage systems to serve Time Machine-enabled Macs.[8][9][10][11][12][13]

See also

References

  1. Lua error in package.lua at line 80: module 'strict' not found.
  2. Lua error in package.lua at line 80: module 'strict' not found.
  3. Lua error in package.lua at line 80: module 'strict' not found.
  4. Lua error in package.lua at line 80: module 'strict' not found.
  5. Lua error in package.lua at line 80: module 'strict' not found.
  6. Lua error in package.lua at line 80: module 'strict' not found.
  7. Lua error in package.lua at line 80: module 'strict' not found.
  8. Lua error in package.lua at line 80: module 'strict' not found.
  9. Lua error in package.lua at line 80: module 'strict' not found.
  10. Lua error in package.lua at line 80: module 'strict' not found.
  11. Lua error in package.lua at line 80: module 'strict' not found.
  12. Lua error in package.lua at line 80: module 'strict' not found.
  13. Lua error in package.lua at line 80: module 'strict' not found. Also see slowfranklin's comment and its replies. To add the guest UAM, add AFPD_UAMLIST="-U uams_guest.so" to the [Global] section in afp.conf.

External links