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
- Overview of the Veritas InfoScale Products Virtualization Guide
- About Veritas InfoScale Solutions support for Linux virtualization environments
- About Kernel-based Virtual Machine (KVM) technology
- About the RHEV environment
- Virtualization use cases addressed by Veritas InfoScale products
- About virtual-to-virtual (in-guest) clustering and failover
- Overview of supported products and technologies
- Section II. Implementing a basic KVM environment
- Getting started with basic KVM
- Creating and launching a kernel-based virtual machine (KVM) host
- RHEL-based KVM installation and usage
- Setting up a kernel-based virtual machine (KVM) guest
- About setting up KVM with Veritas InfoScale Solutions
- Veritas InfoScale Solutions configuration options for the kernel-based virtual machines environment
- Dynamic Multi-Pathing in the KVM guest virtualized machine
- Dynamic Multi-Pathing in the KVM host
- Storage Foundation in the virtualized guest machine
- Enabling I/O fencing in KVM guests
- Storage Foundation Cluster File System High Availability in the KVM host
- Dynamic Multi-Pathing in the KVM host and guest virtual machine
- Dynamic Multi-Pathing in the KVM host and Storage Foundation HA in the KVM guest virtual machine
- Cluster Server in the KVM host
- Cluster Server in the guest
- Cluster Server in a cluster across virtual machine guests and physical machines
- Installing Veritas InfoScale Solutions in the kernel-based virtual machine 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
- About storage to application visibility using Veritas InfoScale Operations Manager
- About Kernel-based Virtual Machine (KVM) virtualization discovery in Veritas InfoScale Operations Manager
- About Red Hat Enterprise Virtualization (RHEV) virtualization discovery in Veritas InfoScale Operations Manager
- About Microsoft Hyper-V virtualization discovery
- Virtual machine discovery in Microsoft Hyper-V
- Storage mapping discovery in Microsoft Hyper-V
- Server consolidation
- Physical to virtual migration
- Simplified management
- Application availability using Cluster Server
- About application availability options
- Cluster Server In a KVM Environment Architecture Summary
- VCS in host to provide the Virtual Machine high availability and ApplicationHA in guest to provide application high availability
- Virtual to Virtual clustering and failover
- I/O fencing support for Virtual to Virtual clustering
- Virtual to Physical clustering and failover
- Recommendations for improved resiliency of InfoScale clusters in virtualized environments
- 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
- About disaster recovery for Red Hat Enterprise Virtualization virtual machines
- DR requirements in an RHEV environment
- Disaster recovery of volumes and file systems using Volume Replicator (VVR) and Veritas File Replicator (VFR)
- Configure Storage Foundation components as backend storage
- Configure VVR and VFR in VCS GCO option for replication between DR sites
- Configuring Red Hat Enterprise Virtualization (RHEV) virtual machines for disaster recovery using Cluster Server (VCS)
- Multi-tier business service support
- Managing Docker containers with InfoScale Enterprise
- About managing Docker containers with InfoScale Enterprise product
- 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
- Limitations while managing Docker containers
- Application visibility and device discovery
- Section IV. Reference
- Appendix A. Troubleshooting
- Troubleshooting virtual machine live migration
- Live migration storage connectivity in a Red Hat Enterprise Virtualization (RHEV) environment
- Troubleshooting Red Hat Enterprise Virtualization (RHEV) virtual machine disaster recovery (DR)
- The KVMGuest resource may remain in the online state even if storage connectivity to the host is lost
- VCS initiates a virtual machine failover if a host on which a virtual machine is running loses network connectivity
- Virtual machine start fails due to having the wrong boot order in RHEV environments
- Virtual machine hangs in the wait_for_launch state and fails to start in RHEV environments
- VCS fails to start a virtual machine on a host in another RHEV cluster if the DROpts attribute is not set
- Virtual machine fails to detect attached network cards in RHEV environments
- The KVMGuest agent behavior is undefined if any key of the RHEVMInfo attribute is updated using the -add or -delete options of the hares -modify command
- 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
- Appendix B. Sample configurations
- Appendix C. Where to find more information
- Appendix A. Troubleshooting
Sample configurations for a Red Hat Enterprise Virtualization (RHEV) environment
Sample configuration for a RHEV-based service group:
group rhev_grp1 (
SystemList = { sys1 = 0, sys2 = 1 }
)
KVMGuest kvmres1 (
RHEVMInfo = { Enabled = 1,
URL = "https://rhevm-server.example.com:443",
User = "admin@internal"
Password = bncNfnOnkNphChdHe,
Cluster = dc2_cluster1,
UseManualRHEVMFencing=1 }
GuestName = rhevvm1
DelayAfterGuestOnline = 20
DelayAfterGuestOffline = 35
)Sample configuration for an AD-based domain:
include "types.cf"
cluster kvmtest (
UserNames = { admin = bQRjQLqNRmRRpZRlQO }
Administrators = { admin }
)
system sys1 (
)
system sys2 (
)
group virt_grp (
SystemList = { sys1 = 0, sys2 = 1 }
)
KVMGuest virt_res (
RHEVMInfo = { Enabled = 1,
URL = "https://rhevm.example.com:443",
User = rhevmadmin@example.com",
Password = codOgoPolOqiDieIf,
Cluster = cluster_NFS,
UseManualRHEVMFencing=0 }
GuestName = VM1
)Sample configuration for a RHEV-based disaster recovery service group:
group VM_SG (
SystemList = { rhelh_a1 = 0, rhelh_a2 = 1 }
TriggerPath = "bin/triggers/RHEVDR"
PreOnline = 1
OnlineRetryLimit = 2
)
KVMGuest kvm_res (
RHEVMInfo = { Enabled = 1, URL = "https://192.168.72.11:443",
User = "admin@internal",
Password = CQIoFQf,
Cluster = RHEV-PRIM-CLUS,
UseManualRHEVMFencing = 1 }
GuestName = swvm02
DROpts = { ConfigureNetwork = 1,
IPAddress = "192.168.74.21",
Netmask = "255.255.252.0",
Gateway = "192.168.74.1",
DNSServers = "143.127.176.14",
DNSSearchPath = "rhevdc.com",
Device = eth0 }
)
requires group STORAGE online global soft
// resource dependency tree
//
// group VM_SG
// {
// KVMGuest kvm_res
// }
group STORAGE (
SystemList = { rhelh_a1 = 0, rhelh_a2 = 1 }
ClusterList = { RHEV_SEC = 0, RHEV_PRIM = 1 }
TriggerPath = "bin/triggers/RHEVDR"
TriggersEnabled = { POSTONLINE }
)
SRDF srdf_res1 (
GrpName = rhevdr
)
SRDF srdf_res2 (
GrpName = rhevdr2
)
// resource dependency tree
//
// group STORAGE
// {
// SRDF srdf_res1
// SRDF srdf_res2
// }
Sample configuration for a multi-resource configuration in a RHEV environment:
system sys1 (
)
system sys2 (
)
group rhevgrp1 (
SystemList = { sys1 = 0, sys2 = 1 }
)
KVMGuest vmres1 (
RHEVMInfo = { Enabled = 1,
URL = "https://rhevm.example.com:443",
User = "admin@internal",
Password = FRGrJRsROrTLgLHlI,
Cluster = vcs_clus,
UseManualRHEVMFencing = 0 }
GuestName = vcsvm1
DelayAfterGuestOnline = 10
DelayAfterGuestOffline = 35
)
group rhevgrp2 (
SystemList = { sys1 = 0, sys2 = 1 }
)
KVMGuest vmres2 (
RHEVMInfo = { Enabled = 1,
URL = "https://rhevm.example.com:443",
User = "admin@internal",
Password = FRGrJRsROrTLgLHlI,
Cluster = vcs_clus,
UseManualRHEVMFencing = 0 }
GuestName = vcsvm2
DelayAfterGuestOnline = 7
DelayAfterGuestOffline = 30
)
Sample configuration for RHEV virtual machine migration:
group rhevgrp (
SystemList = { sys1 = 0, sys2 = 1 }
)
KVMGuest rhevres (
RHEVMInfo = { Enabled = 1,
URL = "https://rhevm.example.com:443",
User = "admin@internal",
Password = AMBmEMnMJmOGbGCgD,
Cluster = rhev_cluster,
UseManualRHEVMFencing=1 }
GuestName = rhevvm1
DelayAfterGuestOnline = 15
DelayAfterGuestOffline = 45
)