Two limitations are therefore worth noting regarding the use of this image file format:
Mac OS X Leopard introduced the concept of the sparse bundle.3 Instead of a single big file, a sparse bundle is a bundle (directory) containing a number of files called bands, each on the order of 8 MB in size. This means even though to the end user the sparse bundle appears as a single file, it is composed of smaller files. As of Mac OS X 10.8, the bands are 8 MiB (8 × 10242 byte) each. When the content of the image changes, one or more band files is changed, created, or deleted. This allows easier shrinking of the amount of space used on the underlying filesystem when a large amount of data is deleted inside the disk image, as long as the code supporting the filesystem inside the image notifies the kernel of the "releasing" of blocks, as happens in filesystems that support SSD "trim" operations to be triggered automatically for de-allocated filesystem blocks.
Sparse bundle advantages over non-diskimage backup for Time Machine:
"Create a disk image using Disk Utility on Mac". Apple. Retrieved August 13, 2020. https://support.apple.com/guide/disk-utility/create-a-disk-image-dskutl11888/mac ↩
"hdiutil(1) OS X Manual Page". Mac Developer Library. Apple. Retrieved January 21, 2013. https://developer.apple.com/library/mac/#documentation/Darwin/Reference/ManPages/man1/hdiutil.1.html ↩
ScottW (November 5, 2007). "Live FileVault and Sparse Bundle Backups in Leopard". macosx.com. Archived from the original on October 29, 2013. Retrieved January 21, 2013. https://web.archive.org/web/20131029200702/http://macosx.com/forums/articles/296196-live-filevault-sparse-bundle-backups-leopard.html ↩
"Backing up Sparse Bundle Images Over SSH". LBackup. Retrieved January 21, 2013. http://www.lbackup.org/synchronizing_disk_images_between_machines ↩