- HOME
vfailover at a glance
Unique features, smooth integration, cost effective. vfailover is the most powerful disaster recovery solution for your virtual environment.Read more...
Documents
Contact
- movis solutions e.U.
- The way you like IT
- +43 676 720 66 55
- info@movis.solutions
- FEATURES
vfailover stands for automation, robust technology and ease integration
Automatic HORCM file creation, Automatic failover plan creation, Replication check, virtual machine monitoring, Stretched and dispersed VMware vSphere HA Cluster support. vfailover comes with many unique features. List of features
Quick Links
- PRODUCT
vfailover all in one package
Minimize risk and simplify your change management.Maintenance Activity
Bring your company back to business as fast as possible.Disaster Recovery
Repair any broken virtual machine configuration.Virtual Machine Repair
Keep everything under control with the end-to-end monitoring tool.Monitoring Tool
Automatic failover plan and HORCM file creation.Automatic Config
- REFERENCES
- SUPPORT
vfailover support matrix
vfailover supports a broad range of VMware vSphere™ versions, HDS storage subsystems and replication technologies. Full support matrix
Virtualization Software
Storage
Subsystems- VMware vSphere™ 5
- VMware vSphere™ 4
- HUS-VM, VSP, USP-V,
- HUS, AMS, ...
- CONTACT
WRITE ORDER CONSISTENCY
vfailover allows the usage of HDS consistency groups to guaranty write order consistency over multiple Ldevs. Write order is necessary if for example a database is made of multiple Ldevs or different applications have dependencies that need such level of protection. If a virtual machine has capacity mapped from two different datastores or additional raw device capacity it may be essential as well to have HDS consistency groups in place.
Here are two different examples showing the configuration of consistency groups:
Example #1
no need to set vfailover parameter "CTGNO"
- Datastore 1 (Consistency Group #1)
- Virtual Machine 1 (Consistency Group #1 - inherited)
- Virtual Disk on Datastore 1 (Consistency Group #1 - inherited)
- Raw Device 1 (Consistency Group #1)
- Raw Device 2 (Consistency Group #1)
- Virtual Machine 2 (Consistency Group #1 - inherited)
- Virtual Disk on Datastore 1 (Consistency Group #1 - inherited)
- Raw Device 3 (Consistency Group #1)
- Virtual Machine 1 (Consistency Group #1 - inherited)
Example #2
vfailover parameter "CTGNO" needs to be set to 5 (hacluster.properties file: CTGNO = 5)
- Datastore 1 (Consistency Group #5)
- Virtual Machine 1 (Consistency Group #5 - inherited)
- Virtual Disk on Datastore 1 (Consistency Group #5 - inherited)
- Raw Device 1 (Consistency Group #5)
- Virtual Machine 2 (Consistency Group #5 - inherited)
- Virtual Disk on Datastore 1 (Consistency Group #5 - inherited)
- Raw Device 2 (Consistency Group #5)
- Virtual Machine 1 (Consistency Group #5 - inherited)
- Datastore 2 (Consistency Group #5)
- Virtual Machine 3 (Consistency Group #5 - inherited)
- Virtual Disk on Datastore 2 (Consistency Group #5 - inherited)
- Virtual Machine 4 (Consistency Group #5 - inherited)
- Virtual Disk on Datastore 2 (Consistency Group #5 - inherited)
- Virtual Machine 3 (Consistency Group #5 - inherited)