Please enter search query.
Search <book_title>...
Veritas InfoScale™ 8.0 Virtualization Guide - Linux
Last Published:
2021-12-21
Product(s):
InfoScale & Storage Foundation (8.0)
Platform: 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
RHEV environment: If a node on which the VM is running panics or is forcefully shutdown, VCS is unable to start the VM on another node
In a RHEV environment, if a node on which a virtual machine is running panics or is forcefully shutdown, the state of that virtual machine is not cleared. RHEV-M sets the VM to UNKNOWN state and VCS is unable to start this virtual machine on another node. You must initiate manual fencing in RHEV-M to clear the state.
This is not a VCS limitation because it is related to RHEV-M design. For more information, refer Red Hat Enterprise Virtualization 3.4 Technical Guide.
To initiate manual fencing in RHEV-M and clearing the VM state
- In the RHEVMinfo attribute, set the UseManualRHEVMFencing key to 1.
UseManualRHEVMFencing = 1
- Override the resource attribute:
hares -override resource_name OnlineRetryLimit
- Modify the OnlineRetryLimit attribute value to 2:
hares - modify resource_name OnlineRetryLimit 2
After you clear the state of the VM, VCS starts the VM on another node.
The following is a sample resource configuration of RHEV-based disaster recovery:
group rhev_sg ( SystemList = { rhelh_a1 = 0, rhelh_a2 = 1 } TriggerPath ="bin/triggers/RHEVDR" PreOnline=1 OnlineRetryLimit = 1 ) KVMGuest rhev_fo ( RHEVMInfo = { Enabled = 1, URL = "https://192.168.72.11:443", User = "admin@internal", Password = flgLglGlgLglG, Cluster = RHEV-PRIM-CLUS, UseManualRHEVMFencing = 1 } GuestName = swvm02 OnlineRetryLimit = 2 ) // resource dependency tree // // group rhev_sg // { // KVMGuest rhev_fo // }