Skip to main content

OpenSolaris, ZFS, iSCSI and OSX - Creative Storage - Part II

In part I of this post, I looked at the simple steps required to setup a relatively simple storage solution using OpenSolaris, ZFS, iSCSI and OSX. This was about a month ago, and I've made some significant changes on how this is used for me.

At the end of the last post I left off on the part dealing with configuration of the iSCSI initiator side of the solution. I stopped here because there were some issues related to the installation and use of the software.

The iSCSI initiator that I was using was Studio Network Solutions GlobalSAN initiator (version 3.3.0.43) which is used to allow for connections to their products. This software will also allow for connections to ANY iSCSI target!

After the configuration of the iSCSI target on the ZFS pool, and installation of the client it was trivial to get the connection established with the storage pool, and it showed up in OSX as a raw disk which had not been formatted.

I proceeded to format the disk as HFS+ and it then mounted as a locally attached disk and I was able to use it as a target for the Time Machine backups. Once selected OSX nicely backed up all of my data to the volume! Perfect! Even the performance of the solution was suprising, as it appeared to significantly outperform previous backups made using USB disks attached to an Airport Extreme, and all of this over my 802.11n network!

Main Problem: Disconnections. Everything worked really well for me if the wireless network connection was active, the iSCSI client was properly started and connected, and Time Machine backups were closely monitored. While this will likely work really well for the guys with hard-wired gigabit connected Mac Pros that are never disconnected from the network or turned off, my MO includes constantly connecting and disconnecting from the network, and also in the middle of performing TM backups.

These disconnections immediately started causing problems with both the iSCSI client connections with the ZFS pool, and with the Time Machine processes associated with the disk. Symptoms included strange errors regarding mis-matches between the sparse disk images and the connected volume, and reconnection issues with the iSCSI client when my laptop gets reconnected to the network without stopping and restarting the iSCSI client.

Solution: CIFS. I always believe that simple solutions are better than complex ones, and although being able to use iSCSI connections to establish disk access seems cool, it doesn't offer a whole lot over standard-old network attached storage. The main reason behind the iSCSI configuration was to get TM to work with the ZFS pool, but there is an alternative - CIFS. There are many posts around the net regarding the use of CIFS and SMB shares for Time Machine backups.

So what I ended up doing is configuring a single ZFS pool for storage and splitting this storage into two - one for general file storage, and one for backups. TM uses sparse disk images which provide the added benefit of limiting the size of the disk image (this is used to limit the amount of disk space which is used by the TM backups - currently 2x the size of my source disk).

By using CIFS as the access method, I also have the ability of backing up my Windows boxes to the same filesystem along-side the TM disk images for each OSX machine.

In part III - when I get time, I will hopefully post the details on the CIFS setup (including security and file permissions), the OSX TM setup, and the Windows backup settings.

I have been using this setup for a few weeks now without a hitch and I have also restored files over the network. The only thing I haven't tested is restoring a full osx install from install DVD's using the TM backup (plan to test this).

Comments

Simon Breden said…
Interesting post, Mark. I look forward to seeing your configuration setup when you get time to make a new post.

Cheers,
Simon

Popular posts from this blog

Local Classified Penny Auction Scam

While there are a lot of new posts regarding the new ways to exploit people using novel techniques and 0day exploits, there continues to be a rash of tried and true methods of coercion.  I want to just walk through a simple example and reflect on how effective these methods continue to be. Many people turn toward online classified sites to buy and sell items online.  This example starts with kijiji.ca which even I've used on occasion to find used electronics and other items.  Doing a search on the site for a " Samsung Galaxy Note 2 " returns a posting from today with someone selling one for an unreasonably priced unit. $125 for a $500 phone?, but what if it's for real?  No harm in just asking some simple questions.  Email sent with some obvious questions regarding the condition and location. About an hour passes before I get a response from what appears to be a legit seller. Notice no answer to the questions I asked, but a friendly pointer at where th

Edmonton HeartBleed Information Session - April 16th, Royal Glenora Club

Since the latest major OpenSSL vulnerability was publicly disclosed, many people and organizations are scrambling to understand, respond and prepare themselves for the future.  Twitter, vendor support channels and media outlets have been quick to cover different angles of the issue but there has been overwhelming amount  of information released. With all this information, it can be difficult to understand what's relevant.  To help clarify we holding a special ISACA sponsored 2-hour session on Wednesday, April 16th, starting at 12:00pm at the Royal Glenora Club.   Benoit and I will be attempting to explain as much of the issue as we can from a technical and non-technical perspective, discussing the vulnerability, its scope with relation to our personal and professional lives and other related concerns such as our trust in the public PKI system.  The second hour we will be an interactive discussion about how others are dealing with problem, questions about related topics,

Touch ID - Distributed Fingerprint Lookup

All the press regarding the new Touch ID fingerprint biometric on Apple's new iPhone has brought some insight into how to misuse this service.  Most of the critics have focused on circumventing the device to gain access or Apple deciding to share the data with the Government. One interesting perspective that I haven't seen covered yet is if the system could be used as a distributed matching system for existing fingerprint image systems.  In an over simplified view of the process, a law enforcement agency can take an acquired fingerprint and search for patterns in the database of collected prints and spit out possible matches. Although Apple states that an API won't be available for apps, it is conceivable that such an interface might exist, and provide the ability to take an acquired print (either from the iPhone hardware or from software) and check it for validity against the stored print. There are some limits to this, as there is likely only going to be one prin