Veritas InfoScale™ 8.0 Virtualization Guide - Linux
- Section I. Overview of Veritas InfoScale Solutions used in Linux virtualization
- Overview of supported products and technologies
- About Veritas InfoScale Solutions support for Linux virtualization environments
- About Kernel-based Virtual Machine (KVM) technology
- About the RHEV environment
- Overview of supported products and technologies
- Section II. Implementing a basic KVM environment
- Getting started with basic KVM
- Veritas InfoScale Solutions configuration options for the kernel-based virtual machines environment
- Installing and configuring Cluster Server in a kernel-based virtual machine (KVM) environment
- Configuring KVM resources
- Getting started with basic KVM
- Section III. Implementing Linux virtualization use cases
- Application visibility and device discovery
- Server consolidation
- Physical to virtual migration
- Simplified management
- Application availability using Cluster Server
- Virtual machine availability
- Virtual machine availability for live migration
- Virtual to virtual clustering in a Red Hat Enterprise Virtualization environment
- Virtual to virtual clustering in a Microsoft Hyper-V environment
- Virtual to virtual clustering in a Oracle Virtual Machine (OVM) environment
- Disaster recovery for virtual machines in the Red Hat Enterprise Virtualization environment
- Disaster recovery of volumes and file systems using Volume Replicator (VVR) and Veritas File Replicator (VFR)
- Multi-tier business service support
- Managing Docker containers with InfoScale Enterprise
- About the Cluster Server agents for Docker, Docker Daemon, and Docker Container
- Managing storage capacity for Docker containers
- Offline migration of Docker containers
- Disaster recovery of volumes and file systems in Docker environments
- Application visibility and device discovery
- Section IV. Reference
- Appendix A. Troubleshooting
- Appendix B. Sample configurations
- Appendix C. Where to find more information
- Appendix A. Troubleshooting
VCS fails to start a virtual machine on a host in another RHEV cluster if the DROpts attribute is not set
In the RHEV environment, every host is part of a RHEV cluster. In a local high availability scenario, hosts forming a VCS cluster should be part of a single RHEV cluster. However, in disaster recovery scenarios, you can configure all hosts on the primary site in one RHEV cluster and all hosts on the secondary site in a different RHEV cluster, though they are all part of the same datacenter. During a site failover, when the DROpts attribute is set, VCS changes the virtual machine host as per the new RHEV cluster.
If the DROpts attribute is not set, VCS does not allow a host from a different RHEV cluster to start the virtual machine. This issue occurs because virtual machine migration does not work across RHEV clusters. Therefore, VCS fails to start the virtual machine on a host that is part of a different cluster.
Veritas recommends configuring hosts in different clusters only in a disaster recovery configuration, and setting the DROpts attribute of the KVMGuest agent. For a local high availability scenario, you do not need to set the DROpts attribute, and all the hosts forming a VCS cluster should be part of the same RHEV cluster.