Skip to main content

Do you really know what they mean when they say "Storage Virtualization" ?

IT managers have been advised to be wary of vendor hype surrounding storage virtualization because it is a technology that is poorly defined, misunderstood and not widely used, according to Dr. Kevin McIsaac, an adviser at research firm Intelligent Business Research Services Pty. (IBRS).

Despite all the hype, McIsaac said that, over the next two years, network-based storage virtualization will remain a niche, while thin provisioning will enjoy rapid adoption in the enterprise.

And while McIsaac readily admits that server virtualization is one of the best IT infrastructure trends to emerge in many years, he said the situation is very different when it comes to storage virtualization.

"This idea of being able to layer virtualization over existing storage arrays is seriously flawed," he warned.

McIsaac said a reasonable definition of storage virtualization is "the abstraction of logical storage from physical storage." However, given the sweeping nature of this definition, it is not surprising that the technology creates confusion.

"The first step in understanding storage virtualization is to recognize that many of today's commonly used techniques and technologies are examples of virtualization, including a file system or a storage array," McIsaac said.


Interesting article this at CW

Comments

Popular posts from this blog

Security: VMware Workstation 6 vulnerability

vulnerable software: VMware Workstation 6.0 for Windows, possible some other VMware products as well type of vulnerability: DoS, potential privilege escalation I found a vulnerability in VMware Workstation 6.0 which allows an unprivileged user in the host OS to crash the system and potentially run arbitrary code with kernel privileges. The issue is in the vmstor-60 driver, which is supposed to mount VMware images within the host OS. When sending the IOCTL code FsSetVoleInformation with subcode FsSetFileInformation with a large buffer and underreporting its size to at max 1024 bytes, it will underrun and potentially execute arbitrary code. Security focus

Splunk that!

Saw this advert on Slashdot and went on to look for it and found the tour pretty neat to look at. Check out the demo too! So why would I need it? WHY NOT? I'd say. As an organization grows , new services, new data comes by, new logs start accumulating on the servers and it becomes increasingly difficult to look at all those logs, leave alone that you'd have time to read them and who cares about analysis as the time to look for those log files already makes your day, isn't it? Well a solution like this is a cool option to have your sysadmins/operators look at ONE PLACE and thus you don't have your administrators lurking around in your physical servers and *accidentally* messing up things there. Go ahead and give it a shot by downloading it and testing it. I'll give it a shot myself! Ok so I went ahead and installed it. Do this... [root@tarrydev Software]# ./splunk-Server-1.0.1-linux-installer.bin to install and this (if you screw up) [root@tarrydev Software]# /op