I tried to do this with the RAIDSetting application from Buffalo, but it failed with complaints about the "The old volume lable is not valid. The next step was to reconfigure the DriveStation as a mirrored array, with an HFS+ volume format. I briefly considered making a disk image on the drive and trying that, but decided I disliked that solution enough that I didn't want to use it even if it worked.Īttempting to use the ZFS pool on the local machine also doesn’t work.
Time Machine refused to recognize it as an acceptable backup volume. I built a nice ZFS mirrored pool out of the two drives, shared it via Personal File Sharing, and mounted it on the other Mac. Disconnecting the entire DriveStation and reconnecting it seemed to fix it. I unmounted that, but attempts to repartition resulted in “resource busy†errors (the other drive repartitioned fine). I tried to make a ZFS pool before repartitioning, which ZFS did without complaint, and which subsequently caused a new volume to mount. The volumes mounted when I first connected it, and I used the Finder to unmount them. As described in the readme, it was necessary to repartition the drives to use the GUID Partition Table. I followed the directions in the Apple ZFS Readme’s Getting Started section. I wanted to try using ZFS first, and if that didn’t work, the DriveStation supports mirroring. I chose it because Fry’s had it (I could get it right now) and I was able to verify that it can operate in JBOD mode. I have an older PowerBook sitting around, so I decided to buy a FireWire external drive and use that as my backup solution (for now). So, at the last minute, Apple tells us that you can’t use an AEBS as a backup server, but you can use Personal File Sharing on another machine running 10.5. From what I understand, Apple has enhanced AFP in Leopard (and by one account, HFS+, or at least the filesystem API) to accommodate the needs of backup software. Although I’m not certain of the precise limitations, they have to do with file ownership and permissions (for example, a user ID on one system is not necessarily the same as a user ID on another system).
Superduper failed to enable ownership mac#
I can speculate as to why: other Mac backup solutions, like SuperDuper!, create a disk image on the target volume to work around limitations in AFP. In fact, it’s the reason I bought the AEBS: I couldn’t be sure that a non-Apple file server would properly support AFP, and I had it on good authority (Apple) that the AEBS would do the trick. It was said, in the months leading up to the release of Leopard, that Time Machine could back up to the AEBS. I’m not too upset that I can’t yet use ZFS for my backups (so long as Apple fixes this in the next six months or so), but I am upset that I can’t use the AirPort Extreme Base Station as a backup file server.
My hope is that Apple will enhance ZFS to support HFS+’s metadata natively, and that will be that. You can hack your way around these limitations, by simply creating additional files on the system and storing the meta data in there, but that’s ugly. Eventually, it makes sense for Apple to move to ZFS as the default file system, but who knows how long that will take? For the time being, HFS+ (Mac OS Extended) file systems store meta data about files that other file systems can’t handle natively.
Now, the bad news: you can’t use ZFS storage pools as your Time Machine Backup drive. Look in the “Mac OS X†section of the downloads area.
Superduper failed to enable ownership full#
To get a beta version of a full read/write ZFS, you need to have an Apple Developer Connection account (the free Online membership is enough). Leopard shipped with a read-only implementation of ZFS. It’s not new news, but it’s still good.
0 kommentar(er)
