Tony Pearson is a Master Inventor and Senior IT Architect for the IBM Storage product line at the
IBM Executive Briefing Center in Tucson Arizona, and featured contributor
to IBM's developerWorks. In 2016, Tony celebrates his 30th year anniversary with IBM Storage. He is
author of the Inside System Storage series of books. This blog is for the open exchange of ideas relating to storage and storage networking hardware, software and services.
(Short URL for this blog: ibm.co/Pearson )
My books are available on Lulu.com! Order your copies today!
Safe Harbor Statement: The information on IBM products is intended to outline IBM's general product direction and it should not be relied on in making a purchasing decision. The information on the new products is for informational purposes only and may not be incorporated into any contract. The information on IBM products is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. The development, release, and timing of any features or functionality described for IBM products remains at IBM's sole discretion.
Tony Pearson is a an active participant in local, regional, and industry-specific interests, and does not receive any special payments to mention them on this blog.
Tony Pearson receives part of the revenue proceeds from sales of books he has authored listed in the side panel.
Tony Pearson is not a medical doctor, and this blog does not reference any IBM product or service that is intended for use in the diagnosis, treatment, cure, prevention or monitoring of a disease or medical condition, unless otherwise specified on individual posts.
Well, I'm back from my adventure. For those who did not follow my tweets, here is a quick recap. Not counting the day we flew from Tucson to Minneapolis, or the day we flew from Memphis back to Tucson, Mo and I spent nine days on the road, covering 1549 miles, or roughly two thirds of the Mississippi River.
Celebrated Fourth of July at the [Wide River Winery] just north of Clinton, IA. Saw "The Last Airbender" at the local cinema.
Buffalo Bill Cody museum was closed on Monday, ate my first loose-meat sandwich lunch at Maid-Rite in Moline, IL, the button museum, aka [Muscatine History and Industry Center] was also closed on Monday, took pictures in the corn fields at Oquawka, IA, ate smoked Carp from [Quality Fisheries, in Niota, IA], ate raisin pie at the Maid-Rite in Quincey, IL. Stayed in a hotel in Hannibal, MO - home of Mark Twain.
Took the Mark Twain paddleboat tour up and down Mississippi river to see Jackson island, almost drove car into the river at Winfield, MO where the Ferry was supposed to be, ate one of everything on the menu at [Fast Eddy's Bon-Air], rode up to the top of the [Gateway Arch] in St. Louis. We stayed in a hotel in downtown St. Louis, MO.
Ate donuts at World's Fair Donuts and frozen custard called "concrete" at [Ted Drewes'] in St. Louis. Popeye museum in Chester, IL, ate dinner at Dixie BBQ in Jonesboro, and took pictures of the huge Superman statue in Metropolis, IL. Stayed in a hotel in Paducah, KY.
Read the murals on the flood walls and toured the [National Quilt Museum] in Paducah, KY. Lunch at Nicky's BBQ just north of Clinton, KY, stopped for photos at Reelfoot Lake in Tennessee. Stayed in a hotel in Memphis, TN.
Tour of [Graceland Mansion], home of Elvis Presley, and [Mud Island], ate dinner at Gus' World Famous Hot & Spicy Chicken, all in Memphis, TN.
Of course, EMC isn't the first, and won't be the last, vendor to [hear the sirens] of Cloud Computing and crash their ships on rocky shores. Just because you manufacture hardware or write software does not guarantee your success as a Cloud service provider.
(FTC disclaimer: I work for IBM. IBM is a successful public cloud service provider, as well as offering products that can be used to deploy a private, hybrid or community cloud, and provides technology to other cloud service proviers.)
An amusing excerpt from Steve Duplessie's post:
"Side Note: There is no such thing as a private cloud. A private cloud is called IT. We don’t need more terms for the same stuff."
I have to agree that when vendors like EMC say "Journey to the Private Cloud", skeptics hear "How to keep your IT administrator job by sticking with a traditional IT approach". Butchers, bakers, candlestick makers and the specialty shop "arms dealers" of Cloud Computing IT equipment may not want to see their market shrink down to a dozen or so service providers, and drum up the fear that "Public Cloud" deployments will "disintermediate" the IT staff.
But does that mean the use of term "Private Cloud" should be discontinued? The US National Institute of Standards and Technology [NIST] offers their cloud model composed of five essential characteristics, three service models, and four deployment models. Here's an excerpt:
Broad network access
Cloud Software as a Service (SaaS)
Cloud Platform as a Service (PaaS)
Cloud Infrastructure as a Service (IaaS)
Like traditional IT, a private cloud infrastructure is operated solely for an organization, so I can see how many might consider the term unnecessary. However, unlike traditional IT, a private cloud may be managed by the organization or a third party and may exist on premise or off premise.
How many traditional IT departments meet the five essential characteristics above? Instead of "on-demand self-service", many IT departments have complicated and lengthy procurement and change control procedures. A few might have "measured service" with a charge-back scheme, and a few others prefer to use a "show-back" aproach instead, showing end users or managers how much IT resources are being consumed without assigning a monetary figure or other penalty. Rapid elasticity? Giving any resource you asked for back can be just as painful because re-purposing that equipment follows the same complicated and lengthy change control procedures.
Just like the term "intranet" refers to a private network that employs Internet standards and technologies, I feel the term "private cloud" is useful, representing an infrastructure that meets the above criteria, employing Public Cloud standards and technologies, that can distinguish itself from traditional IT in key ways that provide business value.
What I do hope "vaporizes" is all the hype, and all the misuse of the Cloud terminology out there.
I use two Cloud-Computing based photo-sharing services, [KodakGallery.com] and [Flickr.com], which serve two completely different purposes.
Formerly, this was Ofoto, but was acquired by Kodak. I started using this service back in 2002, and had over 12,000 photos uploaded over the past 8 years. I was able to share all my photos with my friends and family, and they could simply order whichever prints they want and have them shipped directly to them. They have incredibly high-professional photo-based products, like calendars and coffee table books, that you can produce from your own photos.
Sadly, the fine folks at Kodak Gallery decided they did not want my business anymore, and purged my 36GB of files from their system. To be fair, they did hint that they were having financial problems with an "Archive CD" offering, which would have allowed me to get a set of CDs or DVDs holding the high-resolution graphics of all my uploaded photos. This would have cost $150 or so, and if you uploaded more photos, there was no option to get the "delta" of photos uploaded since your last archive, so it would have cost me $150 every year or so to get an updated "backup" of my files. It seemed expensive and unnecessary at the time, given that I was sure that Kodak was not going out of business anytime soon, and that I was sure they took their own backups of all the photos that people put in their charge.
The problem is that Kodak Gallery was a free service, subsidized by people ordering physical prints and other products. As such, I got lots of email from Kodak every month, offering me free shipping, special promotions, and seasonal discounts. It was so much that I had all email from them automatically routed to a different sub-folder, that I would never look at, unless I was about to make a purchase and needed to find the best coupon code or free shipping option currently offered. This also had the unintended consequence that I missed the following series of notes:
Important: From the Gallery's General Manager (April 17)
Second notice: Our storage policy has changed (April 24)
Final notice: Your stored photos may be deleted (May 8)
We don't want to delete your photos (May 22)
All the notes mentioned the new "Storage Policy", here is a quick excerpt:
"The fact is, we store billions of photos for our 75 million members. The quality storage service the Gallery provides is significant in terms of our business costs.
So that we can provide the highest level of service, we're now asking all Gallery customers to make an annual nominal purchase in exchange for photo storage. We've modified our Terms of Service policy accordingly: if your Gallery photo storage equals 2 gigabytes or less, we're asking you to spend $4.99 annually; if more than 2 gigabytes, $19.99 annually.*
One last thought: We value and appreciate your business, and we want to continue our relationship with you in a spirit of mutual support and benefit. That's always been the Kodak way."
Since they had no response from me, nor saw any purchase activity, my 36GB of files were deleted on June 17. I discovered all of this when I contacted Kodak to find out where my files were last weekend during my "Spring Cleaning". I asked if I could at least get the final set of "Archive CDs", but they told me they were purged completely.
I understand the economy is in a recession, and many free cloud-based services are losing money and going under. I can understand they were faced with tough choices, Kodak opted to switch from a free service to fee-based service.
Albert Einstein defined Insanity as "doing the same thing over and over again and expecting different results." In general, if I am trying to get a hold of someone, and email isn't working, then I try something different, try them by phone, try them by snail mail, and so on. With the deluge of emails, people sometimes declare "email bankruptcy" by deleting everything in their inbox after coming back from vacation, or implement filters to automatically route mail to separate folders. I think it is unrealistic to expect that everybody reads every piece of email that you send them.
I would have liked for Kodak to have done at least one or more of the following, given that I had been such a long time customer, and they had earned hundreds of dollars in revenues from all the purchases, over the years, not just directly from me, but from my friends and family, of photos I uploaded to their website:
Send me a letter after not receiving any response from the first three notices. They sent me promotional materials and offers for 20 percent discounts, so they had my active snail mail address on file correctly. With 75 million users, it would have cost $33 million USD to send out snail mail letters to everyone, but for the subset of power-users who have more than 2GB of files, a snail mail letter might have gotten more $19.99 purchases they needed to stay in business.
Called me on the phone. Yes, they also had my phone number in their database.
Go ahead and charged my credit card on file $19.99 without a purchase, and given me a credit towards a future purchase. Something like: "You have not purchased anything in the last 12 months, so we charged your credit card, per our Terms of Service, but you can use this as a credit towards something in the next 60 days."
On the plus side, my "Spring Cleaning" project was done. You can't organize what you don't have anymore.
Flickr from Yahoo
I started using Flickr back in 2008 to hold photos and graphics for this blog. Flickr holds various sizes of photos that I can use directly with HTML tags. Clicking on the photo in the blog will take you to Flickr's service and allow you to see the large size resolution. The "Lotus Connections" that I have on IBM DeveloperWorks only offers 24MB of photo space, so Flickr was a nice alternative.
Unfortunately, Flickr had adopted a new policy that only the most recent 200 pictures would be visible, and I had already reached 170 photos. Rather than start deleting photos from my older blog posts, I opted to upgrade to the "Flickr Pro" account, with a fee of only $24.99 per year.
Hopefully, by paying an annual fee and choosing a successful and profitable Cloud-Computing company, I won't experience another traumatic loss. However, it does remind me that it is my responsibility to keep my own copies of these photos, just in case.
Fortunately, many "photo product" providers are connected to Flickr. For example, my publisher [<a href="http://www.lulu.com/">Lulu.com</a>] can access my Flickr photos to make photo-based coffee table books. As for my last eight years of memories that were lost, I will just have to treat it as if my house burned down. Rebuild and move on.
Well, today's Tuesday, and you know what that means... IBM Announcements!
This week, IBM has their huge 3Q Launch. This on top of the [2Q results] IBM released yesterday. You can read how the rest of the company did, but it is good to see that IBM grew in both revenue and market share for storage!
As with any IBM launch of this magnitude, there are so many enhancements, I will spread them across several posts.
IBM System Storage TS7610 ProtecTIER® Deduplication Appliance Express
The TS7610 is a smaller appliance than the TS7650 we introduced last year, taking up only 3U of rack space (2U for the disk itself, and a 1U slide rail to simplify maintenance). This is designed for smaller deployments, such as midsized businesses between 100 and 1000 employees that backup 3TB of data per week or less. The unit relies on RAID protected SATA drives. Thanks to the same ProtecTIER data deduplication we have on the TS7650, the TS7610 can hold up to 135TB of backup data on just 5.4TB of disk capacity, with in-line data ingest at 80 MB/sec performance. This little Virtual Tape Library (VTL) emulates up to four TS3500 libraries, with 64 LTO-3 drives and over 8000 virtual tapes. See the [Announcement letter] for details.
The [ProtecTIER Entry Edition] offers a hub-and-spoke approach to replication. You can have up to twelve(12) TS7610 boxes (the "spokes") replicate to a central VTL (the "hub"). This can be ideal for protecting remote office or branch office deployments.
IBM dobules the storage capacity by utilizing 2TB hard disk drives for the N3300 and N3400 series models, maximizes customer satisfaction through Partner Select Bundles (software bundles) for all of the N3000 series (N3300, N3400, N3600), and offers Application and Server Packs (software bundles) for N3400 models.
For the high-end, IBM introduces an enhanced Performance Acceleration Module (PAM II) bundle for N7900 Gateway. This bundle includes two 512GB Solid State Drive PAM II adapters, two dual-port 10GbE TOE network interface cards (NIC), and various software features.
The DS5020 and EXP520 joins their bigger siblings DS5100 and DS5300 in supporting Solid State Drives (SSD), available in 73GB and 300GB capacities. A new air filter bezel is also available for these when used in dusty environments. See the [Announcement letter] for details.
For my friends down in Brazil, A new 2.8 meter length power cord that supports 220-250 volts is now available for all DS4000 and DS5000 series disk systems. Obrigado para o seu negócio!
IBM Tivoli Storage FlashCopy Manager v2.2
I covered this latest release in my post [FlashCopy Manager v2.2] but the marketing team felt we should include it with this launch to get added exposure and visibility.
I'll try to get to the rest in separate posts over the rest of this week.
By combining multiple components into a single "integrated system", IBM can offer a blended disk-and-tape storage solutions. This provides the best of both worlds, high speed access using disk, while providing lower costs and more energy efficiency with tape. According to a study by the Clipper Group, tape can be 23 times less expensive than disk over a 5 year total cost of ownership (TCO).
I've also covered Hierarchical Storage Management, such as my post [Seven Tiers of Storage at ABN Amro], and my role as lead architect for DFSMS on z/OS in general, and DFSMShsm in particular.
However, some explanation might be warranted in the use of these two terms in regards to SONAS. In this case, ILM refers to policy-based file placement, movement and expiration on internal disk pools. This is actually a GPFS feature that has existed for some time, and was tested to work in this new configuration. Files can be individually placed on either SAS (15K RPM) or SATA (7200 RPM) drives. Policies can be written to move them from SAS to SATA based on size, age and days non-referenced.
HSM is also a form of ILM, in that it moves data from SONAS disk to external storage pools managed by IBM Tivoli Storage Manager. A small stub is left behind in the GPFS file system indicating the file has been "migrated". Any reference to read or update this file will cause the file to be "recalled" back from TSM to SONAS for processing. The external storage pools can be disk, tape or any other media supported by TSM. Some estimate that as much as 60 to 80 percent of files on NAS have low reference and should be stored on tape instead of disk, and now SONAS with HSM makes that possible.
This distinction allows the ILM movement to be done internally, within GPFS, and the HSM movement to be done externally, via TSM. Both ILM and HSM movement take advantage of the GPFS high-speed policy engine, which can process 10 million files per node, run in parallel across all interface nodes. Note that TSM is not required for ILM movement. In effect, SONAS brings the policy-based management features of DFSMS for z/OS mainframe to all the rest of the operating systems that access SONAS.
HTTP and NIS support
In addition to NFS v2, NFS v3, and CIFS, the SONAS v1.1.1 adds the HTTP protocol. Over time, IBM plans to add more protocols in subsequent releases. Let me know which protocols you are interested in, so I can pass that along to the architects designing future releases!
SONAS v1.1.1 also adds support for Network Information Service (NIS), a client/server based model for user administration. In SONAS, NIS is used for netgroup and ID mapping only. Authentication is done via Active Directory, LDAP or Samba PDC.
SONAS already had synchronous replication, which was limited in distance. Now, SONAS v1.1.1 provides asynchronous replication, using rsync, at the file level. This is done over Wide Area Network (WAN) across to any other SONAS at any distance.
Interface modules can now be configured with either 64GB or 128GB of cache. Storage now supports both 450GB and 600GB SAS (15K RPM) and both 1TB and 2TB SATA (7200 RPM) drives. However, at this time, an entire 60-drive drawer must be either all one type of SAS or all one type of SATA. I have been pushing the architects to allow each 10-pack RAID rank to be independently selectable. For now, a storage pod can have 240 drives, 60 drives of each type of disk, to provide four different tiers of storage. You can have up to 30 storage pods per SONAS, for a total of 7200 drives.
An alternative to internal drawers of disk is a new "Gateway" iRPQ that allows the two storage nodes of a SONAS storage pod to connect via Fibre Channel to one or two XIV disk systems. You cannot mix and match, a storage pod is either all internal disk, or all external XIV. A SONAS gateway combined with external XIV is referred to as a "Smart Business Storage Cloud" (SBSC), which can be configured off premises and managed by third-party personnel so your IT staff can focus on other things.
See the Announcement Letters for the SONAS [hardware] and [software] for more details.
For those who are wondering how this positions against IBM's other NAS solution, the IBM System Storage N series, the rule of thumb is simple. If your capacity needs can be satisfied with a single N series box per location, use that. If not, consider SONAS instead. For those with non-IBM NAS filers that realize now that SONAS is a better approach, IBM offers migration services.
Both the Information Archive and the SONAS can be accessed from z/OS or Linux on System z mainframe, from "IBM i", AIX and Linux on POWER systems, all x86-based operating systems that run on System x servers, as well as any non-IBM server that has a supported NAS client.