The NetApp/Sun patent battle continues. I don’t see how NetApp can win this, given the Supreme Court’s Teleflex decision, which makes prior art a question that can be appealed all the way to the Supreme Court.
But the company is doggedly pursuing the battle, and Dave Hitz’s recent declaration – which he hoped would remain private – has been unsealed.
It is an illuminating document.
Lame logic
Dave early points to Sun’s Jeff Bonwick’s statement that NetApp’s WAFL was
. . . the first commercial file system to use the copy-on-write tree of blocks approach to file system consistency.
As if that proves anything. Sun is arguing that earlier non-commercial research experimented with those and other techniques, establishing the prior art and invalidating NetApp’s patents. One NetApp patent has already been removed from the litigation and I expect more to follow.
Fear and trembling
Hitz goes on to say
Because Sun is exploiting NetApp’s patented technology for free and creating interest in ZFS by giving it away for free, it does not have to cover the true cost of incorporating ZFS into the Sun Fire X4500 and marketing it. Sun is thus able to undercut NetApp’s pricing on a per gigabyte basis, like any counterfeiter. This negatively affects NetApp’s ability to compete in the storage space. In responding to normal market pressures, NetApp would have to consider shrinking its normal profit margins. Reduced profit margins in this marketplace can be permanent and difficult to quantify.
One would have to believe that if Sun were paying a reasonable license fee to NetApp the Sun Fire x4500 wouldn’t be competitive with NetApp’s products. That doesn’t compute: the x4500 is a box of disks with a commodity motherboard. It’s the packaging density and cost amortization across 48 drives that gives the x4500 its $/GB advantage.
NetApp could do the same tomorrow – and I hope they’re working on it. They’d enjoy the same cost structure as Sun. Sun still has all the costs of building, debugging and marketing a complex product so NetApp would have the cost advantage.
Losing in the court of public opinion
Dave later comments on the public campaign Sun is waging against NetApp:
I am painfully aware that IP litigation is not favorably viewed by many members of the open source community. Indeed, the mere paricipation in a lawsuit can bear a reputational cost. Aside from the obvious monetary costs of protracted litigation and the distraction of resources from normal business functions, if the Court grants Sun’s motion for a partial stay, NetApp will suffer irreparable harm to its reputation because it will prolong this whole matter rather than allowing for a prompt disposition.
Newsflash: NetApp has suffered harm and will suffer further harm no matter how this gets resolved. If they win, they lose. In the court of public opinion it would be better if they lost.
The court did grant the partial stay. And unsealed Dave’s declaration.
The StorageMojo take
So sad and unnecessary. I understand the impulse to protect one’s intellectual property. I’ve done it myself on occasion.
NetApp’s biggest misperception is that WAFL is somehow central to the success they are enjoying today. That was true about 10 years ago. Guys, your average F500 CIO today could care less about WAFL.
NetApp is growing because they offer a compelling value proposition of quality products, relevant services and worldwide support. WAFL certainly supports that, but as NetApp execs note much of their recent success is due to the integration software that NetApp now offers.
WAFL is a small piece of the picture. Sun could copy it line for line and still not have a quarter of what NetApp offers.
NetApp faces challenges. Storage commoditization threatens all vendors traditional 60% gross margins. The GX integration is problematic and the bottom line benefit uncertain. EMC’s move into cloud file services is a clever flanking strategy.
But letting fear drive you isn’t the answer. Boldness and innovation – NetApp’s traditional strengths – is the way to a profitable and high-growth future. Sun is a distraction, not a direction.
Comments welcome, of course. Disclosure: I’ve met Dave Hitz a couple of times and he is a genuinely fine person. If you think I’ve pulled some punches here that’s the reason.
Update: A commenter felt I didn’t get Dave’s point across because I’d edited the quote to what I – perhaps mistakenly – thought were the Most Significant Bits. Here’s the salient part of â‹5 of Dave’s declaration:
5. Sun’s ZFS technology appears to be a conscious reimplementation of NetApp’s innovative WAFL filesystem, as admitted by the creators of ZFS: “The file system that has come closest to our design principles, other than ZFS itself, is WAFL . . . the first commercial file system to use the copy-on-write tree of blocks approach to fie system consistency.”
I still don’t follow the logic that Bonwick’s acknowledgment of WAFL’s technical features means that ZFS is a “conscious reimplementation” of WAFL. Evidently the judge wasn’t persuaded either.
End update.
Relational database management systems have been using the same techniques for decades to maintain transaction-consistent indexes and relational data inside databases. WAFL may indeed be the first implementation of the idea where the “tree of blocks” points to files in a general-purpose file system. But in an RDBMS, the tree of blocks (tree of index pages) typically points to arbitrary row data in the database. What’s the difference? Not much, bits are just bits. The application to a file system seems obvious to me (reasonably skilled in the art), meaning the patent should likely be challenged. Heck, not-so-innovative Microsoft was kicking the same ideas around back in the early 1990s as part of the WinFS file system for the “Chicago” project.
When CIO’s couldnt care less I dont think they’re taking into account the huge performance gains given to their storage infrastructure by WAFL, because by now, the low latency standards set by Netapp are generally taken for granted. But..but WAFL *is* central to high performance because WAFL is not just a filesystem but a filesystem combined with NVRAM that enables low latency request logging and delayed write gathering, two very significant factors if they’re going to be serving millions of requests per second.
From your description above, the legal issues between Sun and Netapp seem to have arisen because of the tree-of-blocks layout which has its uses in fast and low disk-space overhead snapshotting.
Where can I get ZFS to try it out – ? Or get one of Sun’s “x4500” boxes? I would love to pay less than the proprietary NAS vendors are charging – $250k for an NFS filer, what a total ripoff.
One would have to believe that if Sun were paying a reasonable license fee to NetApp the Sun Fire x4500 …
—–
Robin, this is presuming that Sun does not have an enterprise storage strategy to use ZFS for the market segment that NetApp currently services. That… presumes too much.
Mind you I agree with your conclusions regarding the patents and the like. But to say that NetApp has nothing to be afraid of is simply not true. Sun would, if they could, knock NetApp out of the storage market. And no, they’re not so stupid as to think Thumper could do that.
Joe.
The problem for NetApp is that si far thei WAFL was an advantage for them. Now you have ZFS with everything you got in WAFL and more and additionally you also have a support for NVRAM. Actually it is even better because you got support for NVRAM/SSD for ZIL which helps a lot for all synchronous writes but you also got L2ARC which combined with SSD gives you relatively huga cache which is much cheaper than RAM.
Then put on top of it some nice GUI, make it a black box to user, open source and…. there’s nothing to smile for NetApp.
interesting read
robin, here’s dave hitz’ complete quote of sun’s jeff bonwick (page 2 of hitz’ declaration):
“The file system that has come closest to our design principles, other than ZFS itself, is WAFL … the first commercial file system to use the copy-on-write tree of blocks approach to file system consistency.”
you cited only the part after the ellipses and derided hitz for trying to prove something by way of the remainder, but it’s pretty clear that hitz’ point is the part you elided.
what’s up with that?
Peter, I guess I’m missing the point or perhaps I didn’t communicate the issue I saw.
To wit: prior art doesn’t have to be “commercial” to be prior art. If Sun can point to either academic research into these techniques or, as Ryan suggested, common usage in databases, then they’ve got a case for invalidating NetApp’s patents.
I haven’t done that research, so I’m not passing judgement, despite my skepticism. What has changed with the Teleflex decision is that Sun can keep appealing the prior art issue. It used to be that once the trial court decided there was no prior art, there was no appeal. Hence the popularity of East Texas for patent cases.
Teleflex is a much tougher standard for plaintiffs, and as Ryan suggests, the techniques in question may have been widely used in related contexts. If Sun were to lose at trial, they still have a chance to persuade an appellate judge.
Thus my issue with Dave’s Bonwick quote was the qualifier “commercial.” Bonwick’s acknowledgement has no bearing on the issue of prior art.
HTH,
Robin
If ZFS is a violation of NetApp’s rights to WAFL, AMD should sue Intel for Nehalem. x86 single-die quad-core with private L2, shared L3 cache, integrated memory controller and point-to-point link? That doesn’t happen, though. And I think it highlights how silly this is.