Skip to main content

Disaster Recovery on Laptop: VMware SRM with LeftHand VSA!

Nice writeup this. I would too like to test it out, if I ever get the time.

Introduction

As a demo/test I wanted to build a complete SRM setup with both sites being protected. This requires two SRM installations and configurations and two replicated LUN’s. Since I am rather limited in available hardware at the moment, I needed to run every component in a virtual Machine on a single laptop.

Luckily, LeftHand Networks has a virtual SAN appliance, which actually is supported by VMware SRM. This way, I can use a supported SAN, and still use ony one laptop.

All used software (VMware ESX, vCenter, LeftHand VSA and Microsoft SQL Server Express 2005) are available for free (or as evaluation software).

Hardware and host software

I’m running all this on a Zepto Znote 6324W with a Intel Core 2 Duo T9300 (Penryn, 2,5Ghz with Intel VT and Execute Disable Bit), 4GB of RAM and a 200GB 7200RPM SATA2 hard disk.

This laptop is running Microsoft Windows Server 2008 (64-bits), with VMware Workstation 6.5.118166.

More here...

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

OS Virtualization comparison: Parallels' Virtuozzo vs the rest

Virtuozzo's main differentiators versus hypervisors center on overhead, virtualization flexibility, administration and cost. Virtuozzo requires significantly less overhead than hypervisor solutions, generally in the range of 1% to 5% compared with 7% to 25% for most hypervisors, leaving more of the system available to run user workloads. Customers can also virtualize a wider range of applications using Virtuozzo, including transactional databases, which often suffer from performance problems when used with hypervisors. On the administration side, customers need to manage, maintain and secure just a single OS instance, while the hypervisor model requires customers to manage many OS instances. Of course, the hypervisor vendors have worked hard to automate much of this process, but it still requires more effort to manage and maintain multiple operating systems than a single instance. Finally, OS virtualization with Virtuozzo has a lower list price than the leading hypervisor for comme...