Skip to main content

Virtualization : Backup still not mature enough in Virtual World

This user had some mixed experiences:

My company has tried VMware VCB with very mixed results which is not good for a backup solution. When we tried to restore some vms, they appeared as they had crashed. In talking with VMware support they acknowledge this is "an issue" that they're working on.

I don't know what that means, but that's unacceptable for any backup solution.

We've seen that Windows 2008 hyperv has a live backup feature that somehow integrates with vss. This could be the perfect solution if it works. Any news on that?


And this article attempts to cover the backup dilemma in the Virtual World:

Traditional backup systems have a one-to-one relationship with servers. These tried-and-true backup systems and associated software already support storage-area networks (SAN), fiber optics, and the latest operating system and server hardware updates. But they are not geared specifically for the complex world of virtualization, which involves multiple guest operating systems on the same box.

Dave Russell, Gartner Inc.'s vice president of research for servers and storage, outlined three popular strategies for virtualization backups. The most common is putting software agents on each virtual machine (VM) and then using traditional enterprise backup software. A second approach is to create an image of the VM and either use a storage service hosted elsewhere or take daily snapshots of the logical unit number (LUN).



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...