IDC: High Availability Still Matters

By: linuxscribe

March 19, 2013 8:18 pm





It’s kind of nice when people in your industry look at what you’re doing and like what they see.

So when IDC’s analysts examined SUSE’s high availability functionality for SUSE Linux Enterprise and declared it good, we took note.

Specifically, IDC analyst Jean Bozman reviewed the addition of the High Availability Extension for SUSE Linux Enterprise and recognized its importance in a sector that increasingly needs high availability features.

“This aspect of Linux distributions is increasingly important because many business workloads are migrating from Unix systems to Linux systems — and customer expectations for high availability (HA) for those business workloads are rising,” Bozman wrote.

High availability is not something that Linux vendors can really ignore, since more customers than ever are factoring in high availability in their OS decision making.

“Given the rapid growth in Linux server deployments within the enterprise, it is important for all major Linux distributions to provide functionality to address higher levels of high availability and disaster recovery, which can be used, if needed,” Bozman added.

We agree, of course, and this is something out own Kai Dupke recently pointed out in a guest post on Data Center Knowledge.

“HA is still a necessary part of IT, because not every IT department needs all of its services out in the cloud,” Dupke wrote.

Take a look at the IDC report for yourself, and find out more about how SUSE delivers on the high availability promise.

0 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 5 (0 votes, average: 0.00 out of 5)
You need to be a registered member to rate this post.

Categories: Expert Views, SUSE Linux Enterprise, SUSE Linux Enterprise High Availability Extension

Disclaimer: As with everything else in the SUSE Blog, this content is definitely not supported by SUSE (so don't even think of calling Support if you try something and it blows up).  It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test, test, test before you do anything drastic with it.