{"id":42830,"date":"2017-11-07T10:52:20","date_gmt":"2017-11-07T16:52:20","guid":{"rendered":"https:\/\/eshop.macsales.com\/blog\/?p=42830"},"modified":"2019-10-18T11:00:33","modified_gmt":"2019-10-18T16:00:33","slug":"can-apfs-be-used-with-time-machine-boot-camp-and-file-vault","status":"publish","type":"post","link":"https:\/\/eshop.macsales.com\/blog\/42830-can-apfs-be-used-with-time-machine-boot-camp-and-file-vault\/","title":{"rendered":"Can APFS be used with Time Machine, Boot Camp, and File Vault?"},"content":{"rendered":"

\"Apple<\/p>\n

macOS High Sierra contains many new features and capabilities, but APFS (Apple File System) is certainly one of the biggest changes<\/a>. Changing the primary file system used by the Mac, or for that matter, any computer system is a big deal. Apple has only changed the default Mac<\/a> file system twice in its 33-year history.<\/p>\n

Macintosh File System (MFS) was the original file system introduced along with the Macintosh in January 1984. It was designed to meet the demanding needs of a 400 KB floppy disk. The Hierarchical File System (HFS) followed in September 1985, and the last file system upgrade was Hierarchical File System Plus (HFS+), which was released with Mac OS 8.1 in January 1998.<\/p>\n

APFS and Time Machine, Boot Camp, and File Vault<\/strong>
\nWhile there have been some minor upgrades to HFS+ over the years, the Mac’s file system has stayed pretty much the same since 1998. That makes the new APFS file system a big deal. And like any big deal, there’s a lot to understand about how APFS will work with existing Mac apps and services, including Time Machine, Boot Camp, and File Vault.<\/p>\n

Related articles:<\/strong> Translating Apple\u2019s New High Sierra & APFS Compatibility Document<\/a>, <\/strong>How to Revert a drive from APFS back to HFS+<\/a><\/p>\n

We’re going to primarily look at these three Apple-provided apps and services, but third-party apps may also be affected by the change to APFS. It’s a good idea to check any file system utility you may be using for APFS compatibility.<\/p>\n

Time Machine<\/strong>
\nIn its current incarnation, the Time Machine app<\/a> is mostly compatible with APFS; that is, you can back up an APFS formatted drive using Time Machine, as well as restore files from a Time Machine backup to an APFS formatted drive. However, there are some very important caveats that Time Machine users should be aware of.<\/p>\n

Time Machine drives must be formatted in HFS+. Time Machine uses the magic of hard links, a feature that HFS+ file systems have to catalog and keep track of which files in a backup make up the current version of an app, document, or directory. Hard links are just one of three types of file linking that HFS+ supports, the others being symbolic links and aliases.<\/p>\n

\"Time
(Time Machine in its current incarnation is unable to use an APFS formatted volume for backups.)<\/strong><\/figcaption><\/figure>\n

APFS, on the other hand, does not support hard links. When you convert an HFS+ formatted volume to APFS, any hard links found during the conversion process are automatically changed to symbolic links, thus breaking your Time Machine backup into a collection of almost useless files. Luckily, installing macOS High Sierra won’t automatically convert Time Machine drives to APFS, but it’s possible to change the drive’s format to APFS from within Disk Utility or via the Terminal app. Resist the temptation to go all APFS; Time Machine will not cooperate with you.<\/p>\n

If you do accidentally convert a Time Machine drive to APFS, the Time Machine app will no longer recognize the drive as a backup drive. If you select the old Time Machine drive within the Time Machine app as a backup destination, you’ll be confronted with an option to erase all of the content on the selected drive and reformat it as HFS+. (Actually, Time Machine will just warn you that it must first erase the destination drive, but the reason is because the drive has an incompatible format.)<\/p>\n

Until Apple releases a new version of Time Machine that makes use of the APFS feature set, such as snapshots to replace file linking, your Time Machine backup must remain formatted as HFS+.<\/p>\n

Boot Camp<\/strong>
\nBoot Camp, the ability to run Windows<\/a> (or other OSes) as a native (non-virtualized) OS on your Mac, remains, for the most part, compatible with APFS, although as with Time Machine, there are a few gotchas to be aware of:<\/p>\n

Your Windows volume, sometimes referred to as the Boot Camp volume, isn’t affected by conversion to APFS; it will remain an NTFS formatted volume. So, there are no special steps to take in preparing for a High Sierra upgrade or a conversion to APFS.<\/p>\n

\"Boot
(Boot Camp’s Windows support software does not include drivers that would allow your Windows installation to read or write to APFS volumes.)<\/strong><\/figcaption><\/figure>\n

Probably the issue most likely to be encountered is the inability to see or share files on an APFS volume with your Windows environment. At the moment, Apple’s Boot Camp drivers, and any currently available Windows tools, are unable to read or write to APFS volumes. This leaves APFS volumes on your Mac unusable from within Windows.<\/p>\n

If you need to access Mac files, you could use an HFS+ formatted volume as a go-between until Apple, Microsoft, or a third party produces a utility for accessing APFS formatted drives from within Windows.<\/p>\n

Another related issue you may encounter occurs when you try to set the macOS as the startup drive from within Boot Camp. Once again, Windows can’t see APFS drives, so you’ll likely see an error message about being unable to locate the macOS boot volume.<\/p>\n

The current workaround is to use the Mac’s Startup Manager to select which environment you wish to boot into. Here’s how to do it:<\/p>\n

Restart your Mac, and hold down the option key.<\/p>\n

Release the option key when you see the startup manager appear on the display.<\/p>\n

Select the macOS from the list of available startup disks, and then click return.<\/p>\n

Your Mac will start up using the selected operating system.<\/p>\n

If you wish to always start up in the macOS, you can use the Startup Disk preference pane in System Preferences to set the desired startup disk.<\/p>\n

FileVault<\/strong>
\nApple says that HFS+ volumes that use FileVault are converted to APFS volumes, which have built-in encryption capabilities. While the statement is true, it’s a bit ambiguous, so let’s see if we can shed some light on the subject.<\/p>\n

With the initial release of macOS High Sierra, only the selected startup volume that is the target of the install is converted to APFS, and then only if it’s an internal SSD<\/a>. External SSDs<\/a> appear not to be converted, and remain as HFS+ disks (this behavior may change in subsequent updates).<\/p>\n

\"While
(While the FileVault name remains, APFS formatted volumes will use the file system’s built-in encryption system.)<\/strong><\/figcaption><\/figure>\n

If the startup drive uses FileVault, the conversion to APFS will result in a volume that uses APFS’s built-in encryption scheme and not the older FileVault encryption.<\/p>\n

Fusion-based drives, at least during the initial release of High Sierra, aren\u2019t converted to APFS, regardless of whether they use FileVault encryption or not.<\/p>\n

Any additional non-Fusion drive attached to your Mac may be manually converted to APFS. If the drive uses FileVault encryption<\/a>, it will be replaced with APFS based encryption.<\/p>\n

File Sharing<\/strong>
\nFile sharing should continue to work, with one exception. The older AFP (Apple File Protocol) isn’t supported on APFS volumes. If you’re using the older AFP system for sharing files, an APFS formatted volume won’t be visible to the file sharing service.<\/p>\n

\"Sharing
(Sharing APFS volumes requires the use of SMB. You can set the sharing options for SMB in the Sharing preference pane.)<\/strong><\/figcaption><\/figure>\n

The workaround is to use SMB (Server Message Blocks) as the preferred file-sharing protocol. It’s also possible to use NFS (Network File System), though Apple recommends SMB.<\/p>\n

To specify SMB sharing on your Mac:<\/p>\n

Open System Preferences, and select the Sharing preference pane.<\/p>\n

Select File Sharing, and then click the Options button.<\/p>\n

Make sure there is a checkmark in the “Share files and folders using SMB” box, and then click the Done button.<\/p>\n

Third-Party File Utilities<\/strong>
\nYou should check with the app developer to ensure that any third-party file utilities you may be using or are planning to use are compatible with macOS High Sierra and\/or the APFS file system. This is especially true of cloning and backup utilities, such as the always popular Carbon Copy Cloner<\/a> and SuperDuper<\/a>, which have a wide following in the Mac community.<\/p>\n

APFS: What to Expect in the Near Future<\/strong>
\nApple will likely green light APFS for Fusion drives once they’re satisfied that they’ve worked the bugs out of the conversion process. When Fusion drive support is released, I expect it will be in a macOS High Sierra update that will likely make the APFS upgrade to Fusion startup drives mandatory, just like SSD upgrades from Fusion drives were in the initial release.<\/p>\n

The other near-future change I expect, and let me hedge that by calling it the far end of the near future, is an update to Boot Camp drivers that will include the ability to read\/write to APFS volumes.<\/p>\n

I imagine an update to Time Machine that can use APFS volumes as a backup destination is some time further out, perhaps as far as macOS 10.14. But that’s just my own uninformed opinion, based on the idea that Time Machine does currently work, and there’s always a need for a major app update to be part of a new version of an operating system.<\/p>\n

\n

More on APFS:<\/strong><\/p>\n