{"id":248,"date":"2008-08-23T22:58:38","date_gmt":"2008-08-24T06:58:38","guid":{"rendered":"http:\/\/mike.peay.us\/blog\/?p=248"},"modified":"2009-09-19T22:12:58","modified_gmt":"2009-09-20T06:12:58","slug":"i-learned-all-about-time-machine-so-you-dont-have-to","status":"publish","type":"post","link":"https:\/\/mike.peay.us\/blog\/archives\/248","title":{"rendered":"I learned all about Time (Machine) so you don’t have to"},"content":{"rendered":"

\"\"I’ve been learning a lot about the Time Machine<\/a> feature of Apple’s OS X 10.5 (Leopard) and wanted to take the time to share my experience. In a nutshell, Time Machine watches the files that get modified on your system and copies them to a secondary hard drive or network volume so that you have automatic backups available for anything that was deleted or modified.<\/p>\n

It is a very nice user experience and it takes a lot of the work out of making backups. Of course, by taking work out Apple is really just making decisions for the majority of users and for most users, that decision is quite acceptable. I’m not most users. Fortunately, Apple directly or indirectly provides methods for changing the behavior of much of the OS and Time Machine is no exception. Here are many of the things that I’ve gathered over the last few months that might benefit you if you want to get more out of your experience.<\/p>\n

Overview<\/strong><\/p>\n

\"\"I won’t go into too much detail as I’m going to presume you’ve already used Time Machine and are familiar with how it works. Generally, it performs a backup of your system every hour to an external drive. It is\u00a0efficient\u00a0in that only the modified\u00a0files are copied. Hourly copies are kept for for 24 hours, daily copies for a month, and weekly copies until the destination drive fills up. You are free to put other data on that Time Machine disk, but it will eventually consume all available space.<\/p>\n

Space is pretty efficiently used in that a file is copied only if it has changed but ineffecient in that a small change to a large file results in the entire file being backed up again. This can be a problem if the file really is big and changes frequently. This is the case with the virtual hard disk used for a virtual machine under VMware Fusion<\/a> or Parallels Desktop<\/a>.<\/p>\n

Backing-up to a network volume<\/strong><\/p>\n

Any self-respecting geek has more than one computer in his or her home. Often times, you are using a laptop and have a dedicated computer with more storage sitting by your TV or in the den, closet, or garage. Unfortunately, while Time Machine can back up to a network volume, by default it only supports a specially presented volume served via Apple’s network filling protocol (AFP<\/a>) from Leopard Server. You can back up to other choices (e.g., Windows or Linux) via Microsoft’s filing protocol (CIFS<\/a>). To do this, you first need to have a native Apple file system to copy the data to.<\/p>\n

Creating a sparseimage<\/strong><\/p>\n

OS X has supported disk images since the beginning but has recently added a format called sparseimage that starts small but grows as more data is added to it. To use a network volume, you first need to create the image that your machine will be storing the actual data in. Type the following on a mac creating the disk on a local hard drive first:<\/p>\n

hdiutil create -library SPUD -size $SIZESPEC<\/span> -fs HFS+J -type SPARSEBUNDLE \\
\n-tgtimagekey sparse-band-size=262144 -volname \"Backup of $MACHINENAME<\/span>\" \\
\n$MACHINENAME_$MAC<\/span>.sparsebundle<\/code><\/p>\n

Here are\u00a0explanations\u00a0on the options that you’ll want to change:<\/p>\n

$SIZESPEC \u2013 the size of the virtual disk when filled. A good choice is twice the size of what you’re backing up.<\/p>\n

$MACHINENAME – The name of your machine<\/p>\n

$MAC – The network address of the primary network interface without separators (e.g., aabbccddeeff0011). You can get this from System Profiler or Network Utility.<\/p>\n

For education purposes, here is some explanation of some of the other items:<\/p>\n

-fs HFS+J \u2013 make the filesystem HFS+ with Journaling (the default OS X filesystem)<\/p>\n

sparse-band-size \u2013 the size of the ‘chunks’ that make up the sparseimage (they aren’t just one single file). Normally, the images are made in 8M chunks but those perform quite poorly over the network. The value provided above represents 128M chunks (2 * 128 * 1024 512-Byte-Blocks = 262144 = 128MB) which is a good size for a hard disk backup.<\/p>\n

Copying the image to to the network volume is as simple as dragging the sparseimage file via the Finder or do it in the terminal:<\/p>\n

cp -r $MACHINENAME_$MAC.sparsebundle \/Volumes\/path\/to\/destination
\n<\/code><\/p>\n

The last part is to tell the system to allow any network volume as a destination and not just AFP:<\/p>\n

defaults write com.apple.systempreferences TMShowUnsupportedNetworkVolumes 1<\/code><\/p>\n

Using just part of a drive<\/strong><\/p>\n

For some reasons you’ll see below, I wanted to limit the usage of the destination drive local to the system. Normally, Time Machine will use all the space of an external drive chosen as the destination. If you are storing other information on it, that can become a problem. The solution is to convert the physical Time Machine destination volume into a disk image.<\/p>\n

The first step is to create a disk image with the same information above. Next, mount the newly created disk image:<\/p>\n

hdiutil mount \/path\/to\/created\/imagefile<\/code><\/p>\n

You can also mount it simply by double-clicking on the disk image file. You’ll then copy the contents of the current Time Machine volume to the created disk image. Note, it is best to ensure Time Machine is disabled as you don’t want anything changing as you are copying it:<\/p>\n

sudo asr restore --source \/Volumes\/srcvol --target \/Volumes\/Backup\\ of\\ $MACHINENAME<\/code><\/p>\n

asr is Apple’s System Restore utility and it performs copy between volumes but ensures that everything is copied properly. You need the sudo portion to have the command be able to access every file which may not be the case if run just as yourself.<\/p>\n

Of course, this copy can take some time depending on the speed of your system but mostly due to the size of the data being copied.<\/p>\n

Once completed, you can unmount the disk image and configure Time Machine to use the disk that the disk image is stored on. Time Machine is smart enough to use the image if it sees it (the file has to be at the top-level of the destination hard drive).<\/p>\n

Trigger a Time Machine backup from the command-line
\n<\/strong><\/p>\n

If you ever want to trigger a Time Machine backup on a system from the command-line, perhaps on a remote system via ssh, issue the following command:<\/p>\n

\/System\/Library\/CoreServices\/backupd.bundle\/Contents\/Resources\/backupd-helper<\/a> -auto<\/code><\/p>\n

Exclude an individual file from being backed up
\n<\/strong><\/p>\n

You can exclude files from being backed up (like previously mentioned virtual disks) using the GUI in the Time Machine preferences (under Options), but it can also be done using the extended attributes in the command-line:<\/p>\n

xattr -w com.apple.metadata com_apple_backup_excludeItem \/path\/to\/file\/to\/exclude<\/code><\/p>\n

Similarly, you can see if a file is being excluded but listing the extended attributes:<\/p>\n

xattr -l \/path\/to\/file\/in\/question<\/code><\/p>\n

Hide the Time Machine disk in the Finder
\n<\/strong><\/p>\n

If you aren’t getting all fancy and writting to a disk image, you may want to hide the destiation disk. You can do that just by making the volume invisible:<\/p>\n

SetFile -a V \/path\/to\/Time\/Machine\/Volume
\n<\/code><\/p>\n

Conclusion
\n<\/strong><\/p>\n

I hope this has been helpful to you and that with the information are able to make a useful tool even more useful. To give credit where credit is due, I’ve included below the links to where much of the information was originally found.<\/p>\n

Update<\/strong><\/p>\n

20090527 I’ve revised the sparse-band-size value from 1G to 128M which is the largest band currently support in 10.5.7. Files with larger band files cannot be mounted in 10.5.7. Once I determine the correct procedure for converting an old image, I’ll post a new article. In the meantime, you can get more information here<\/a>.<\/p>\n

Reference<\/strong><\/p>\n

10.5:\u00a0Set up Time Machine on a NAS in three easy steps<\/a><\/p>\n

10.5: Improve networked Time Machine performance<\/a><\/p>\n

Man page for hdiutil<\/a><\/p>\n

Man page for asr<\/a><\/p>\n

Exclude Items From Time Machine Backup With Contextual Menu<\/a><\/p>\n

Time Machine Exposed!<\/a><\/p>\n

Hide Time Machine’s icon in the Finder<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

I’ve been learning a lot about the Time Machine feature of Apple’s OS X 10.5 (Leopard) and wanted to take the time to share my experience. In a nutshell, Time Machine watches the files that get modified on your system … Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":false,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2}},"categories":[12,3],"tags":[],"class_list":["post-248","post","type-post","status-publish","format-standard","hentry","category-apple","category-geek"],"aioseo_notices":[],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/p4vft-40","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/mike.peay.us\/blog\/wp-json\/wp\/v2\/posts\/248","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/mike.peay.us\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/mike.peay.us\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/mike.peay.us\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/mike.peay.us\/blog\/wp-json\/wp\/v2\/comments?post=248"}],"version-history":[{"count":6,"href":"https:\/\/mike.peay.us\/blog\/wp-json\/wp\/v2\/posts\/248\/revisions"}],"predecessor-version":[{"id":316,"href":"https:\/\/mike.peay.us\/blog\/wp-json\/wp\/v2\/posts\/248\/revisions\/316"}],"wp:attachment":[{"href":"https:\/\/mike.peay.us\/blog\/wp-json\/wp\/v2\/media?parent=248"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/mike.peay.us\/blog\/wp-json\/wp\/v2\/categories?post=248"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/mike.peay.us\/blog\/wp-json\/wp\/v2\/tags?post=248"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}