Portable Home Directories Part 1: What a Mess!

Now that I've tried it myself, I've very much enjoyed the advantages that having a network home account has offered. I've also rather disliked some of the disadvantages. Ultimately, the biggest drawback has been that when our production crew is doing a lot of rendering, my home account slows to a crawl and I can't get work done. Okay, I can, but not without a lot of swearing, and the fellas in the other cubicles just ain't digging that, believe me.

After some water-cooler-side conversation, and some excellent comments by my excellent readers, I've decided I might be just be a perfect candidate for something that may offer the best of both worlds.

Portable Home Directories (PHDs), as they're called by Apple, essentially allow a user to keep and work from a local copy of his network home account. The local account is synced up with the network account using various strategies, which I'll talk about in a bit. It's essentially an intelligent implementation of Windows' crappy Roaming Profiles. The big difference is those strategies I mentioned.

Windows' Roaming Profiles are problematic, particularly in production environments where users store a lot of data, because Windows simply hard syncs those profiles at login and logout. This means that if you've generated a lot of data in any given session, you're in for a long wait when you log out — and another long wait if you log into another machine — while Windows syncs your local and network profiles. It's a nice idea — giving you the centrality of a network account and the responsiveness of a local one — but it fails in practice because it is, essentially, dumb, causing the sync process to ruin the experience.

The experience we're going for here is, of course, seamlessness. Or as close to it as possible. So: I want to be able to log in to my workstation and have the responsiveness and normalcy of a local account, but I then want to be able to log in to another workstation and have my documents follow me throughout a given facility. Moreover, I want the synchronization of said documents to be as invisible as possible to the user. It should "just work." With as little waiting and confusion as possible.

This is, of course, easier said than done.

Apple takes a noble stab at this with its Portable Home Directory settings. See, where Microsoft simply syncs account data at login and logout, Apple affords some granularity in what gets synced and at what times. Apple gives you precise control over what gets synced, as well as allowing for not just login and logout syncing, but periodic syncing as well. Smart! And it could make all the difference.

But I'm getting ahead of myself again. Let's actually step through the process of creating a Portable Home Account. I'll show where it shines and where it falls apart for me.

Activate Mobility Preferences

• This all starts in Workgroup Manager. So fire that up and navigate to the user you want on Portable Homes.
• Make sure that user's current home account is a Network Home Account (i.e., it lives on a server somewhere).
• Click the "Preferences" button from the toolbar, and then open the "Mobility" pane. This is where all the action happens.

  

Set Account Creation Options

• The first thing to set up is how and when the local portable account is created. Click on the Account Creation tab and set Manage: to Always.
• Since I already have a network home account that I've been using from an NFS share (on a non-Apple server), I set my user to "Create mobile account when user logs in" using the "default sync settings." I assumed this would copy everything over from the network account to the local drive and start the ball rolling fresh, but that's not what happened. More on that in a bit.

  

• Under Account Creation's Options tab I set a custom path that pointed to a folder that contained a local version of my home account that I'd rsynced previously. Again, I did this thinking it would speed the initial sync process, but that turned out to not be the case.

  

Set Sync Rules

• Finally it's time to define how the syncing between local and network homes will behave. This is the real genius behind the Portable Home Directory system, and what distinguishes it from Roaming Profiles.
• First under the Rules tab you have "Login & Logout Sync." This allows you to set specific items to sync only at login and logout. The suggested defaults for this are mainly your account settings, i.e. your entire ~/Library folder. This is quite sane, and I stuck with this setting.

  

• Note the "Merge with user's settings" checkbox. I initially checked this, but later found it problematic. It was useful on my first sync, but it doesn't appear to track deletions and such, so I ended up disabling it.
• Also of note is the "Skip items" section. This allows for what rsync users would call exclusions. This also greatly speeds syncing as you can exclude unneeded items such as cache and trash. I stuck with the sane defaults here as well.
• Next up are your Background Sync settings. Again, very sane defaults are provided: We back up your entire home account, periodically, in the background. Skip the usual suspects and don't merge.

  

• Finally, under Options, we can set the frequency with which the server will run the background sync.

  

• I also set the option to "Show status in menu bar." This, as you'll see, becomes quite useful for the way I ultimately ended up using this feature.

Some Disclaimers

Portable Home Directories are actually not specifically intended for the sort of use-case we're applying them to here. PHDs are actually designed for users with laptops that come and go onto a network that is also populated with stationary workstations. It's really made to be used in conjunction with network home accounts, allowing laptop users to use network home accounts without being completely tethered to the network.

So to be clear, this is an experiment. I'm doing things a bit outside the norm. (I mean, what fun would it be if I weren't.) And any problems I had were likely because of this fact. Still, it's hinted at in the documentation that PHDs can be used for users of non-portable machines to some advantage, so I wanted to see how we could apply them to our (okay, my) particular situation.

I started off a bit outside the realm of the typical first time setup. I had two things at the outset that essentially represented a test of how we might migrate to a PHD-style system: I had a network home account already populated with data, and I had a copy of that data on a local hard drive. This represents our typical user. But I was also hoping that I'd be able to use these to get the Portable Homes process underway more speedily. This was not the case at all.

Initial Experiences

The first thing that happened when I logged into my newly Portable Homes-activated account was that I was greeted with a prompt asking me if I wanted to create a portable home.

I chose to do so ("Yes"), since that was pretty much what I was here to do. And upon login I was greeted, not with my previously set up network home account nor my rsynced local account, but rather with the standard boilerplate skel account you see when creating a new user. Worse, the server seemed to get confused as to where my home account should be placed on the local drive. Though I had defined it on my server as a custom path, it seemed to want to go in a folder called "User" on the specified drive, no matter what I entered for the custom path. Apparently, for me anyway, the custom path — and my hopes of speeding the sync process — just plain old didn't work.

After this I decided to try again. I moved my custom folder off the local drive and, in Mobility Preferences, simply defined the drive I wanted to use for my Portable Home. I also chose to "Merge with user's settings" for this go 'round under the Rules section of the Mobility prefs. The thought was that this should pull down my network home account and create a local version from it. And this is exactly what happened. And for a time life was good and I thought I was done. I thought I'd found my magic settings. But the next day I logged in to find that once again my account had reverted back to the default, first-login settings. Yikes!

(Here I'd just like to point out the benefits of having a backup of your entire home account if you're going to play around with this. Or just use a spare, dummy account. I actually did lose data numerous times during my testing, as you'll see in Part 2.)

After poking around a bit I discovered that my machine had logged me into my network home. Or at least that's where the Finder went when I hit Command-Shift-H. But my home account settings were the defaults, not my network home account settings. WTF? Logging out and logging back in I found myself in what I considered to be the right local location, and all my custom settings had returned. But this was clearly getting weird and flaky. And no matter how I configured things, the weirdness persisted. The biggest problem, though, was the fact that my local and network home accounts never synced in the background. And that was sort of the most important part.

Manual Sync

For a time I used Portable Home Directories the only way I could get it to work for me. Remember that tickbox to "Show status in menu bar?" Well, it turns out that you can use this menubar widget to manually sync your local and network home accounts. And manual syncing actually worked okay for me. In fact, it was the only way I could get my network and local data in sync.

During this time I pretty much using the default Mobility settings, but my account was on my Work drive. Portable Homes had placed it at:

/Volumes/Work/systemsboy.xahomes

for some strange reason, but I could live with that. Every so often — particularly if I thought I might be going to another machine and logging in as myself — I'd hit "Sync Home Now" in the Menubar pulldown.

This would begin the Home Sync process. The process is far from immediate, but it's not too slow. It takes a few minutes. Once it's done I can verify that my network and local homes are synced up.

Conflicts that the service couldn't resolve were handled similarly to iPhone-to-AddressBook conflicts, though, with the usual PHD flakiness: often conflicts occurred where they shouldn't have.

But the biggest problem with Manual Sync was that logging in to another computer failed. A popup alert appeared telling me I was unable to log in at this time because "an error occurred." Great.

I was really hoping for this to be seamless, of course. But it just may not be possible with this particular setup. The best I can get out of Portable Homes so far is not much better than a glorified rsync script with a pretty GUI for running it and some semblance of conflict resolution. And it completely breaks my ability to log into other computers.

Conclusion (For Now)

In the end I decided that my troubles were likely due to the fact that I was not working in the typical Mac OS X idiom. It's my guess that Portable Homes failed for me in this instance mainly because my network home account is on a completely different, non-Apple server, one that my Mac Server is not set up to share as a network home location. I would venture that if you set Portable Homes up just like it says in the manual, using Apple kit and AFP and the like (possibly AFP reshares would work), Portable Homes works like a charm. But if you don't you'll get some strangeness like I did. Ah, the joys of the bleeding edge!

On my first shot at Portable Homes I experienced a number of surprises and inconsistencies. While Portable Homes is a great idea, and in theory looks to be perfect for someone like me, there are major pitfalls in a complex, multi-platform environment that prevent it from being usable for much of anything. But Portable Homes has potential and I plan to delve more into how to get it working for us in our complex environment. In our next installment I'll be trying a setup more closely aligned with the Apple-sanctioned method for implementing PHDs. We'll see how it goes.

Software Update Server

I can't believe I never wrote this up, but I've been using the Software Update Server included with Mac OS X Leopard Server since I upgraded the servers at my old job. If your network — or Apple's servers — are ever slow to get updates, having your own centralized SU Server can make a world of difference. But it's most useful when you have a bunch of Macs you need to update all at once. Try doing ten or so over the Internet at the same time. You'll get errors and failures, and you'll kill your network pretty quickly as all those updates come in at once. But updating a lab full of Macs from your own dedicated Software Update Server will not only not fail, it'll actually be quite fast since your using only internal bandwidth, of which you should have plenty. Setting one of these up is pretty easy, but there are a couple gotchas I always have to remember. So here we go.

1. Activate the service in Server Admin.

   

2. Configure the service. I like to configure the SU Server to "Automatically copy all new updates from Apple." This is the easiest, and I like things easy. But otherwise I use the default settings.

   

3. Start the service and list the updates. And here's one of the gotchas: when you first start the service there is no indication that anything is happening. There is no progress bar and nothing will appear in the list of updates. But in fact the SU Server is downloading all the updates (several Gigs) in the background. The easiest way to prove that this is actually happening is to run the df command, then run it again. You should see your root drive getting gradually fuller as the server downloads the updates. This first download will take a long time. I like to let it go overnight.

   

4. When you return the next morning, the list should be populated with all the available updates, as seen above. (Also, you see about 10-15 GBs of data in the Software Update Server's data store, which is here: /usr/share/swupd/html/content/downloads/.) The last step then — and the thing I often forget — is to tell your client Macs where to get their Software Updates. To do this you'll need a computer list in Workgroup Manager. Add any computers you want to use your SU Server to the list. Then go to the Preferences pane for the group and select Software Update. Set the URL for the SU Server to: http://server.domain.com:8088/index.sucatalog

   

5. After saving that configuration, logging out and logging back in should be all you need to do on your clients to pick up the server. After doing so, run Software Update and you'll see the name of your SU Server in the menubar of the interface. This confirms you're successfully getting updates from the server.

   

Congrats! You're not a total moron. Enjoy!

UPDATE:

Reader Dennis points out in the comments that individual clients can be configured to look to the SUServer for updates without being part of a WGM group or managed by the server at all. This is done by modifying a preference on the client system, which you would do thusly:

sudo defaults write /Library/Preferences/com.apple.SoftwareUpdate CatalogURL "http://systemsboy.su.server.com:8088/"

That command can, of course, be sent en masses using Apple Remote Desktop's "Send Unix Command" directive.

And, if you want to revert to the standard method of checking for updates, looking at Apple's servers, delete the "CatalogURL" entry in the preference file by running:

sudo defaults delete /Library/Preferences/com.apple.SoftwareUpdate CatalogURL

Thanks for the tip, Dennis!

More Data Recovery

It's been a bad couple of weeks for data loss in the Systems Boy household. Fortunately, it's been a fairly good week for data recovery, so we've mostly broken even, minus the time lost recovering data, of course.

Most recently, something seems to have taken a large (by which I mean everything) bite out of a very important CSS file. See, we tend to use Coda to build sites at our house, and we tend to work over the network as the most expedient means to that end. Now, working on a website over the network is not without its perils, as I'm sure you're aware. Particularly if you're working wirelessly, and particularly if you're working on a server of unknown reliability. So, a very awesome someone I know (okay, yes! I have a girlfriend!) was doing exactly that when all of a sudden her CSS file appeared to be completely empty. Mind you, she was not working on the file. She merely had it open while she worked on another document in another tab. But after switching to the CSS tab, the CSS file — which she'd been working on obsessively for about a week — appeared to be empty.

Now I've had the same thing happen to me after a network dropout — or, more likely, a server disconnect — and the solution in my case was to simply shut down and restart Coda. Mine was largely a cosmetic issue brought on, I assume, by Coda's inability to reconnect to the documents after a disconnect. So I told her to simply restart Coda, confident that the problem would correct itself. But it didn't. Even after restarting Coda, still no CSS joy. The file was there, but it was completely empty!

This is the point at which panic generally sets in. (And no, that is not a reference to the makers of Coda.)

If there's anything I've learned in my near-ten years of professional systems work, it's that data is rarely ever completely wiped out in a single stroke. And if there's anything else I've learned, it's not to panic. So I coolly, calmly set about the task of recovering the file while my exhausted and infuriated sweetheart went to bed.

The first thing I did was to check the server to see if any backups had been made. I know that her provider, and some of the software she uses, make automatic backups from time to time. So I downloaded anything and everything I could find from the server that might prove useful, including a backup of the entire site for safekeeping. I soon discovered that there was nothing even remotely recent enough to contain the missing CSS file. So I started looking in the local home account, first by grepping for anything with "css" in the name. Some Coda cache files came up, some of which were fairly recent, but none failed to yield the data I was searching for. I searched /tmp as well, to no avail.

Finally, after a couple of hours of downloading and grepping and searching and hoping, I was about ready to give up. As a last ditch effort I decided to use the find command on the entire local hard drive:

find / -name *.css*

This command will search the entire file system for any file whose name contains the string ".css." And it turned out to be the winner. The command yielded a ton of useless results, many of which came from application documentation. But in the end a Coda cache file turned up in:

/private/var/tmp/501

Of all places!

Moreover, this file had a time stamp very near the time of the disappearing data. So I made a copy of it (okay, I made, like, four copies of it) and uploaded it to the server. The next day my sweetie confirmed: I'd found the file! The day was saved!

So remember, people: Stay calm, and always try find before giving up the ghost. And for poops sake, make a backup!

Whew! That was close!

Hudzee

Or is it Hudzee?

A friend of mine is trying his hand at product creation. Based on his 15+ years of systems experience in the world of commercial video production he's determined a burgeoning need for storage storage: a case for your hard drives.

See, hard drives have become so cheap that they're actually the best per-gigabyte bang for your buck when it comes to data storage. So more and more clients are simply archiving everything to standard, internal ATA hard drives. Once a project's done, pull the drive from the machine or (firewire case) and stick it on a shelf. Many of my friend's clients have stacks of these drives, wrapped in anti-static bags, piled one on top of another on a shelf in some closet somewhere. It's an ugly way to treat your drives, and, moreover, it's not necessarily the safest way either.

Enter Hudzee. (Or is it Hudzee?)

Hudzee is a tape case for your hard drive. Remember tape? Back in the day it's what we stored all our video on. It's also what we used to archive data. It's slow and expensive, but it's very good for archiving. And it's slowly going the way of the dodo. But the thing about tapes is that every tape you bought — whether for data storage or video — came with something no hard drive does: A case. A nice, big, cushioned, stackable, hard, plastic case. Hudzee is just such a beast only sized precisely for your hard drive.

Now I will say, Hudzee's creator is a friend of mine. And I'm obviously motivated by my desire to see him succeed. But I also have to say, I think that Hudzee is a great idea. I've just received my first production unit. The build quality is nice. The materials are solid, and plenty strong to safely hold a standard, 3.5" hard drive, and there is plenty of cushioning inside. A solid, but easy-to-open, latch keeps the case securely shut. My drive feels safe in here. Safer than it's ever felt before.

The other great thing about the Hudzee is that, like tape cases of yore, it features a label card. Finally, you can know what's on that drive without putting it back in the machine. Or, worse, labeling it with tape or some such sticky nastiness. Now a simple glance at the case is all you need.

So if you've got — or will have — a stack of hard drives sitting on a shelf in some back room somewhere, you might consider getting some Hudzee. (Or is it Hudzees?) They're $8 bucks a pop, or $65 bucks for a box of 10. Cheap compared to the price of a hard drive. Absolute chump change compared to the pricelessness of your data.

Order some online today. You know you want to.

Twitter: No, I Fully Admit, I Don't Get It

The buzz around Twitter is, frankly, reaching a pitched and utterly annoying frenzy. Some of the latest stuff I've read, though, has inspired me to add my voice to the throngs. Yes, that would be you people.

Now let me start by saying I don't use Twitter. I don't even have an account. And this leads me to my first beef about Twitter: the barrier to entry. "Come on!" you say, "All you need is an email address and a password." Yes, This is true. But in a world where a user such as myself already has about 80 trillion user accounts, and about 20 trillion of those are in now-defunct, out-of-style, unused social networks, one starts to think a bit more carefully about signing up for anything at all anymore. I mean, Jesus, I still get email from Friendster. Fucking Friendster! And don't even get me started on the whole online dating thing. Suffice to say, I've been doing this for a while now, and I've gotten gun-shy.

But the other, bigger, more hidden barrier to entry — the one no one talks about much when they talk about Twitter — is the fact that to Twitter "properly" takes a certain kind of work. It's not like starting a blog; you can't just start Tweeting in a vacuum and hope to get anywhere. No, Twitter requires effort and strategy. Effort in the following of other Twitter users and, eventually, strategy in being followed by other Twitterers. It's not that I mind work — I certainly do my fair share of it — but the goal of Twitter work seems to be following and/or being followed. And I've never been much of a pack animal.

A friend of mine, who has also been reading about, but so far refrained from joining, Twitter, recently remarked (in a Facebook status update, no less):

"I've been reading about this for the past couple days and it seems to me what Twitter does is take educated and mobile people who would form a kind of elite regardless of the technology of the day, and offers them another way to seperate [sic] themselves from the masses while at the same time allowing them to assert that they are in fact very well-connected."

This describes a feeling I've had for some time about Twitter, but have been unable to put into words. Twitter has an air of exclusivity that I find off-putting. Defensive article titles like, "Twitter Quitters Just Don't Get It" don't do much to ameliorate that feeling. And so, something that at it's heart is perfectly benign, and potentially even useful or entertaining — an extremely micro micro-blogging platform with a small per-post character limit — has become something that fosters a certain sense of resentment from those of us who choose not to partake of its offerings. If there's been a Twitter backlash, it's probably largely due to the defensive posture of its users. And I believe it's partly this posture that my friend is talking about.

It seems to me that the other part of my friend's argument — and the other part of my hesitance at signing up — is context. Like I said, I'm kinda burnt out on the whole social networking thing. But I recently joined Facebook just the same, and I've stuck around. And the reason I can stomach Facebook is context. When you sign up for Facebook you immediately have a context, and that context is your friends. What better context could there be? Everyone wants to stay connected with friends, and Facebook handles this better than any social network I've used so far. I think Twitter's lack of context, while certainly being part of its charm, is another barrier to entry for many. For the technologically savvy (which I consider myself to be), and for those inclined to experiment with social networks in general (which I no longer consider myself to be so much), the lack of context is far less vexing. And those seem to be just the sorts of people using Twitter — the elite my friend is referring to. They seem to have figured out a way to make Twitter genuinely useful. For them. But by outward appearances, Twitter's context seems to be less about staying connected and more about appearing clever amongst a group of peers.

To those elite Twitter lovers though, I say bully for you. You get on that Twitter client-of-the-day (I must admit, some of the client apps look beautiful enough to make me want to join purely from an interest in interface design) and you tweet your little hearts out. I bear no grudge against this. I just personally have no desire to be any more connected than I already am. I don't see how Twitter will be useful or enjoyable for me. I don't get Twitter, and I'm pretty sure I just don't really want to.

And bully for me too. 'Cause guess what? I don't get Flickr either. Or MySpace. Or feed readers. In fact, there's a whole lot of stuff I don't get.

And all the snide little articles in the world aren't going to change my mind.