Jon Toigo is a respected writer and consultant for all areas
of network storage. He contributes to a variety of magazines and trade publications,
and oversees the Data Management Institute. He has published books including “The
Holy Grail of Network Storage Management.” His Drunken Data blog has a monthly
readership of over 500,000.
Jon previously wrote an article for Enterprise Systems Journal on Novell Storage Manager, saying that the product “… strikes data management gold.”
Our CEO, David Condrey, gave Jon a sneak peek at Novell File Reporter months before it was released in the Novell File Management Suite. Jon was impressed with what he saw and looked forward to working with the entire suite once it was released.
Jon has had some follow-up discussions with David Condrey and has reviewed the Novell File Management Suite himself, and recently posted these comments on a blog posting entitled “Everything We Need to Know About How to Screw Up IT…”
"The more I learn about
it, the more I like the Novell File Management Suite. NFMS is about
policy-based file management based on user role: a concept I like a
lot. I had a chat with them today and one of their really smart folks
commented that in this DO MORE WITH LESS environment, people seem to be
preoccupied with the WITH LESS component more than the DO MORE component.
As we have been ranting about at length here over the past couple of months,
folks are still trying to throw hardware at the data burgeon — relying on thin
provisioning, de-dupe, on-array tiering, etc. functionality joined at the hip
to their array controllers to tackle the difficult problem of data
management. Technically speaking, data management has virtually
nothing to do with hardware."
And later…
"Folks, the thing about
data management is that it focuses on data management, not on capacity
management. Novell’s stuff is best of class in the products I have
reviewed. Dave Condrey’s team has done an out-fracking-standing job with
this software, which lets you set policies for data movement based on user
role. Is it perfect? Nope. Will the Britney Spears files that
that HR guy downloads at lunch be exposed to the same policies as the files
created by his legitimate work effort? Possibly, depending on how you
write your exclusion policies. But, now we have a sustainable way to tag
a file, expose it to appropriate integrity, protection, and security services,
and move it around infrastructure in an intelligent and compliant way.
AND IT IS ALL INVISIBLE TO THE USER."
Comments