Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. Start calculating Now!
Configure VirtualBox Failover in a Windows Server 2012 R2 Cluster
Has anyone ever configured VirtualBox as a Clustered role in Windows Server 2012 R2? I want to avoid using Hyper-V if possible, because our backup application by default supports VirtualBox. I can use Hyper-V, but that would require me to run a conversion on the backup file, which translates to increased downtime.
All I can get from Google is how to setup a cluster whithin virtualbox, where 2 or more guests are running server 2012 on a Virtualbox host.
I want to setup 2 physical servers in a cluster (This is already up and running. The clustered storage is a synology rackstation with a LUN setup connected to this cluster.). Then setup the failover such that if Host1 is running Virtualbox that has 2 guests and fails, Host2 will start Virtualbox and spin up the 2 guests that Host1 was running.
Any help is appreciated.
Thanks!
All I can get from Google is how to setup a cluster whithin virtualbox, where 2 or more guests are running server 2012 on a Virtualbox host.
I want to setup 2 physical servers in a cluster (This is already up and running. The clustered storage is a synology rackstation with a LUN setup connected to this cluster.). Then setup the failover such that if Host1 is running Virtualbox that has 2 guests and fails, Host2 will start Virtualbox and spin up the 2 guests that Host1 was running.
Any help is appreciated.
Thanks!
Do more with
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
ImageManager is included in the box. The documentation for setting it up is rather poor but that's how you can schedule all of the incrementals to be merged into the parent to keep things relatively simple.
A separate server would be required with VirtualBox set up on it to provide instant restore services. That's the way the StorageCraft documentation reads.
Upon complete failure of the backed up machine/VM use VB to spool up the backup image with no conversion required.
Some downtime would be required to bring the original machine/VM back online.
A separate server would be required with VirtualBox set up on it to provide instant restore services. That's the way the StorageCraft documentation reads.
Upon complete failure of the backed up machine/VM use VB to spool up the backup image with no conversion required.
Some downtime would be required to bring the original machine/VM back online.
We already have Imagemanager running and managing the backup folders. We have 2 additional servers with VirtualBox on them. What we really want to accomplish is some kind of High Availability in Virtualbox. If we spin up a VM on node1 and node1 fails, I'd like node2 to pickup the vm from node1.
If high availability is important then deploy a 2 node Hyper-V cluster with central JBOD via clustered Storage Spaces. That's three components for a Converged Hyper-V Cluster. It's an inexpensive option and gives the VMs running on it some resilience to hardware failure.
Having two stand-by servers for restoration goes above and beyond what we do for any backup solution. Most of our setups are done in such a way as to restore from backup if there is a failure or we have the above cluster configuration in clients as small as 15 seats.
Having two stand-by servers for restoration goes above and beyond what we do for any backup solution. Most of our setups are done in such a way as to restore from backup if there is a failure or we have the above cluster configuration in clients as small as 15 seats.
We have a Synology Rackstation with a ton of storagespace and a dell equalogic san. I was really hoping for a way to failover the Virtualbox =/.
The Dell SAN would be your VM storage point? if that's the case then two identical nodes set up with the LUNs on both would be the ticket.
We do two cluster types as a rule: SOFS (Scale-Out File Server) for SMB backend storage for Hyper-V compute clusters. Fabric is four 10GbE paths via two switches between SOFS and Hyper-V. All of this is essentially built-in to the OS.
With VirtualBox you'd be *NIX/*BSD through the solution stack (VirtualBox site).
We do two cluster types as a rule: SOFS (Scale-Out File Server) for SMB backend storage for Hyper-V compute clusters. Fabric is four 10GbE paths via two switches between SOFS and Hyper-V. All of this is essentially built-in to the OS.
With VirtualBox you'd be *NIX/*BSD through the solution stack (VirtualBox site).
Premium Content
You need an Expert Office subscription to comment.Start Free Trial