My latest articles are up at SearchVMWare.com. I go over how I set up a file server VM to connect via the Microsoft iSCSI initiator to a SATABoy storage array in the first article. In the second article I provide a Powershell and a VBScript script (your choice) that backs up the file server VM onto another ESX host using the command-line “p2vtool.exe.”
From the Part I:
“This two-part article series will outline a way to provide some redundancy for a file server virtual machine without the use of a SAN for VMFS storage or VMotion. The first part will discuss the initial setup of the file server virtual machine. The second part will discuss a scripted synchronization of the source virtual machine (VM) to another ESX server for manual recovery. Depending on your service up-time requirements, a manual fail-over of a virtual machine without the use of VMware HA could be acceptable. While these articles discuss a scenario with a file server virtual machine, the technique discussed could be used with any server that has a system drive that changes infrequently.”
Read the rest of Part I at SearchVMware.com.
From Part II:
“What would happen if your physical server running VMware ESX Server were to fail? If you don’t have failover options in place, you’d be in trouble. The good news is that you can eliminate this worst-case scenario without buying more hardware. You just need a redundant virtual machine (VM) file server.”
Read the rest of Part II at SearchVMware.com.
Happy Reading!
Technorati Tags: VMware, P2V, Business Continuity, iSCSI
0 Responses to “Can’t afford VMotion? Try a manual failover with my latest articles”