Veritas InfoScale™ 7.3.1 Virtualization Guide - Linux on ESXi
- Section I. Overview
- Overview of Veritas InfoScale solutions in a VMware environment
- Overview of the Veritas InfoScale Products Virtualization Guide
- Introduction to using Veritas InfoScale solutions in the VMware virtualization environment
- Introduction to using Dynamic Multi-Pathing for VMware
- About the Veritas InfoScale components
- About Veritas InfoScale solutions support for the VMware ESXi environment
- Virtualization use cases addressed by Veritas InfoScale products
- Overview of Veritas InfoScale solutions in a VMware environment
- Section II. Deploying Veritas InfoScale products in a VMware environment
- Getting started
- Veritas InfoScale products supported configurations in an VMware ESXi environment
- Storage configurations and feature compatibility
- About setting up VMware with Veritas InfoScale products
- Veritas InfoScale products support for VMware environments
- Installing and configuring storage solutions in the VMware virtual environment
- Getting started
- Section III. Use cases for Veritas InfoScale product components in a VMware environment
- Storage to application visibility using Veritas InfoScale Operations Manager
- About storage to application visibility using Veritas InfoScale Operations Manager
- About discovering the VMware Infrastructure using Veritas InfoScale Operations Manager
- Requirements for discovering vCenter and ESX servers using Veritas InfoScale Operations Manager
- How Veritas InfoScale Operations Manager discovers vCenter and ESX servers
- Information that Veritas InfoScale Operations Manager discovers on the VMware Infrastructure components
- About the datastores in Veritas InfoScale Operations Manager
- About the multi-pathing discovery in the VMware environment
- About near real-time (NRT) update of virtual machine states
- About discovering LPAR and VIO in Veritas InfoScale Operations Manager
- About LPAR storage correlation supported in Veritas InfoScale Operations Manager
- Application availability using Cluster Server
- Multi-tier business service support
- Improving storage visibility, availability, and I/O performance using Dynamic Multi-Pathing
- Use cases for Dynamic Multi-Pathing (DMP) in the VMware environment
- About Dynamic Multi-Pathing for VMware
- How DMP works
- About storage visibility using Dynamic Multi-Pathing (DMP) in the hypervisor
- Example: achieving storage visibility using Dynamic Multi-Pathing in the hypervisor
- About storage availability using Dynamic Multi-Pathing in the hypervisor
- Example: achieving storage availability using Dynamic Multi-Pathing in the hypervisor
- About I/O performance with Dynamic Multi-Pathing in the hypervisor
- Example: improving I/O performance with Dynamic Multi-Pathing in the hypervisor
- About simplified management using Dynamic Multi-Pathing in the hypervisor and guest
- Example: achieving simplified management using Dynamic Multi-Pathing in the hypervisor and guest
- Improving I/O performance using SmartPool
- Improving data protection, storage optimization, data migration, and database performance
- Use cases for Veritas InfoScale product components in a VMware guest
- Protecting data with Veritas InfoScale product components in the VMware guest
- Optimizing storage with Veritas InfoScale product components in the VMware guest
- About SmartTier in the VMware environment
- About compression with Veritas InfoScale product components in the VMware guest
- About thin reclamation with Veritas InfoScale product components in the VMware guest
- About SmartMove with Veritas InfoScale product components in the VMware guest
- About SmartTier for Oracle with Veritas InfoScale product components in the VMware guest
- Migrating data with Veritas InfoScale product components in the VMware guest
- Improving database performance with Veritas InfoScale product components in the VMware guest
- Simplified storage management with Veritas InfoScale product components in the VMware guest
- Setting up virtual machines for fast failover using Storage Foundation Cluster File System High Availability on VMware disks
- About use cases for Storage Foundation Cluster File System High Availability in the VMware guest
- Storage Foundation Cluster File System High Availability operation in VMware virtualized environments
- Storage Foundation functionality and compatibility matrix
- About setting up Storage Foundation Cluster File High System High Availability on VMware ESXi
- Planning a Storage Foundation Cluster File System High Availability (SFCFSHA) configuration
- Enable Password-less SSH
- Enabling TCP traffic to coordination point (CP) Server and management ports
- Configuring coordination point (CP) servers
- Deploying Storage Foundation Cluster File System High Availability (SFCFSHA) software
- Configuring Storage Foundation Cluster File System High Availability (SFCFSHA)
- Configuring non-SCSI3 fencing
- Configuring storage
- Enabling disk UUID on virtual machines
- Installing Array Support Library (ASL) for VMDK on cluster nodes
- Excluding the boot disk from the Volume Manager configuration
- Creating the VMDK files
- Mapping the VMDKs to each virtual machine (VM)
- Enabling the multi-write flag
- Getting consistent names across nodes
- Creating a clustered file system
- Storage to application visibility using Veritas InfoScale Operations Manager
- Section IV. Reference
Mapping the VMDKs to each virtual machine (VM)
Map each of the created VMDK files to each VM. The example procedure illustrates mapping the VMDKs to the cfs01 node: all steps should be followed for each of the other nodes.
To map the VMDKs to each VM
- Shut down the VM.
- Select the VM and select Edit Settings....
- Select Add , select Hard disk and click Next.
- Select Use an existing virtual disk and click Next.
- Select Browse and choose DS1 data store.
- Select the folder cfs0 and select shared1.vmdk file and click Next.
- On Virtual Device Node select SCSI (1:0)
and click Next.
- Review the details to verify they are correct and click Finish.
- Since this is the first disk added under SCSI controller 1, a new SCSI controller is added.
Modify the type to Paravirtual, if that is not the default, and check that SCSI Bus Sharing is set to None, as this is key to allow vMotion for the VMs.
- Follow steps 3 to 8 for the rest of disks that will be added to each of the VMs.
For the example configuration, the parameters for steps 5-7 are given in the table below:
Data Store
VMDK Name
Virtual Device
DS1
cfs0/shared1.vmdk
SCSI 1:0
DS2
cfs0/shared2.vmdk
SCSI 1:1
DS3
cfs0/shared3.vmdk
SCSI 1:2
DS4
cfs0/shared4.vmdk
SCSI 1:3
DS5
cfs0/shared5.vmdk
SCSI 1:4
The final configuration for the first node of the example cluster (cfs01):
Now follow the same steps for each node of the cluster and map each VMDK file to the VM following the instructions above. Once all the steps are completed, all the VMs should have access to the same VMDK files. Note that at this point, all the VMs are still powered off and that multi-writer flag has not been enabled yet (it will be done in the next step). Any attempt to power on the VMs in this state will prevent a second VM start because it will violate the restrictions to access a VMDK by only a host at a time.