Veritas InfoScale™ 7.4.1 Virtualization Guide - Linux on ESXi
- Section I. Overview
- About Veritas InfoScale solutions in a VMware environment
- Section II. Deploying Veritas InfoScale products in a VMware environment
- Getting started
- Understanding Storage Configuration
- Section III. Use cases for Veritas InfoScale product components in a VMware environment
- Application availability using Cluster Server
- Multi-tier business service support
- Improving storage visibility, availability, and I/O performance using Dynamic Multi-Pathing
- How DMP works
- Improving data protection, storage optimization, data migration, and database performance
- Protecting data with InfoScale product components in the VMware guest
- Optimizing storage with InfoScale product components in the VMware guest
- Migrating data with InfoScale product components in the VMware guest
- Improving database performance with 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 setting up Storage Foundation Cluster File High System High Availability on VMware ESXi
- Configuring coordination point (CP) servers
- Section IV. Reference
Storage configurations and feature compatibility
All block storage topologies that are supported with ESXi are supported when Storage Foundation is running inside a Virtual machine. The storage specific details are hidden for Storage Foundation by VMware hence FC, iSCSI and locally attached disks are supported.
Table: vSphere features compatible with shared storage configurations
VM storage configurations | Compatible vSphere features | |||
---|---|---|---|---|
vMotion | DRS | VMware HA | VMware Snapshots | |
VMDK on VMFS | Y | N | Y | N |
Physical and Virtual RDM with FC SAN | N | N | N | N |
Physical and Virtual RDM with iSCSI SAN | N | N | N | N |
VMDK on NFS | N | N | N | N |
iSCSI inside guest | Y | Y | Y | Y * |
NFS inside guest (using Mount agent) | Y | Y | Y | Y * |
* Taking snapshots is possible if VCS and all applications are fully stopped. Before reverting to the snapshot, shutdown VCS and all applications and then revert to the snapshot. Ensure that no software updates or configuration changes related to VCS have been applied post the snapshot.
Refer to appendix A for more on known limitations before moving to a configuration with VCS in the guest.