Skip to main content

A happy Virtual Iron customer's story

"We deployed VI in January and migrated 12 of our servers onto the platform. In the past four months, each node has locked up once, taking the virtualized servers on it down, as well, with no automatic move to a different node - VI is still trying to figure out what happened.. Aside from that, I have been very pleased, and certainly appreciate the much lower price tag."

I followed up with Tanya and asked if the lockups resulted in any lost data. Here's what she said:

"No, we didn't lose anything except uptime. As soon as I identified that a node was down, I was able to migrate the VMs to a different node and bring them right up. I haven't lost any data; I think my issues are actually with the Virtual Manager, but that is by no means an expert opinion."

Link

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