Veritas Storage Foundation and High Availability Solutions Application Note: Support for HP-UX Integrity Virtual Machines

Veritas Storage Foundation and High Availability Solutions Application Note: Support for HP-UX Integrity Virtual Machines HP-UX 11i v3 5.0.1

Veritas Storage Foundation and High Availability Solutions Application Note: Support for HP-UX Integrity Virtual Machines The software described in this book is furnished under a license agreement and may be used only in accordance with the terms of the agreement. Product version: 5.0.1 Document version: 5.0.1.1 Legal Notice Copyright 2010 Symantec Corporation. All rights reserved. Symantec, the Symantec logo, Veritas, Veritas Storage Foundation, CommandCentral, NetBackup, and Enterprise Vault are trademarks or registered trademarks of Symantec corporation or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners. The product described in this document is distributed under licenses restricting its use, copying, distribution, and decompilation/reverse engineering. No part of this document may be reproduced in any form by any means without prior written authorization of Symantec Corporation and its licensors, if any. THE DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID. SYMANTEC CORPORATION SHALL NOT BE LIABLE FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING, PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE INFORMATION CONTAINED IN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE. The Licensed Software and Documentation are deemed to be commercial computer software as defined in FAR 12.212 and subject to restricted rights as defined in FAR Section 52.227-19 "Commercial Computer Software - Restricted Rights" and DFARS 227.7202, "Rights in Commercial Computer Software or Commercial Computer Software Documentation", as applicable, and any successor regulations. Any use, modification, reproduction release, performance, display or disclosure of the Licensed Software and Documentation by the U.S. Government shall be solely in accordance with the terms of this Agreement.

Symantec Corporation 350 Ellis Street Mountain View, CA 94043 http://www.symantec.com

Technical Support Contacting Technical Support Symantec Technical Support maintains support centers globally. Technical Support s primary role is to respond to specific queries about product features and functionality. The Technical Support group also creates content for our online Knowledge Base. The Technical Support group works collaboratively with the other functional areas within Symantec to answer your questions in a timely fashion. For example, the Technical Support group works with Product Engineering and Symantec Security Response to provide alerting services and virus definition updates. Symantec s support offerings include the following: A range of support options that give you the flexibility to select the right amount of service for any size organization Telephone and/or Web-based support that provides rapid response and up-to-the-minute information Upgrade assurance that delivers software upgrades Global support purchased on a regional business hours or 24 hours a day, 7 days a week basis Premium service offerings that include Account Management Services For information about Symantec s support offerings, you can visit our Web site at the following URL: www.symantec.com/business/support/index.jsp All support services will be delivered in accordance with your support agreement and the then-current enterprise technical support policy. Customers with a current support agreement may access Technical Support information at the following URL: www.symantec.com/business/support/contact_techsupp_static.jsp Before contacting Technical Support, make sure you have satisfied the system requirements that are listed in your product documentation. Also, you should be at the computer on which the problem occurred, in case it is necessary to replicate the problem. When you contact Technical Support, please have the following information available: Product release level

Hardware information Available memory, disk space, and NIC information Operating system Version and patch level Network topology Licensing and registration Customer service Router, gateway, and IP address information Problem description: Error messages and log files Troubleshooting that was performed before contacting Symantec Recent software configuration changes and network changes If your Symantec product requires registration or a license key, access our technical support Web page at the following URL: www.symantec.com/business/support/ Customer service information is available at the following URL: www.symantec.com/business/support/ Customer Service is available to assist with non-technical questions, such as the following types of issues: Questions regarding product licensing or serialization Product registration updates, such as address or name changes General product information (features, language availability, local dealers) Latest information about product updates and upgrades Information about upgrade assurance and support contracts Information about the Symantec Buying Programs Advice about Symantec's technical support options Nontechnical presales questions Issues that are related to CD-ROMs or manuals

Documentation Your feedback on product documentation is important to us. Send suggestions for improvements and reports on errors or omissions. Include the title and document version (located on the second page), and chapter and section titles of the text on which you are reporting. Send feedback to: docs@symantec.com Support agreement resources If you want to contact Symantec regarding an existing support agreement, please contact the support agreement administration team for your region as follows: Asia-Pacific and Japan Europe, Middle-East, and Africa North America and Latin America customercare_apac@symantec.com semea@symantec.com supportsolutions@symantec.com

Veritas Storage Foundation and High Availability Solutions Support for HP-UX Integrity Virtual Machines This document includes the following topics: Introduction HP Integrity Virtual Machines terminology About HP Integrity Virtual Machines Supported Storage Foundation and HP IVM versions Supported VCS and IVM versions Supported configurations using IVM Storage Foundation supported configurations using IVM Storage Foundation High Availability supported configurations using IVM Storage Foundation Cluster File System supported configurations using IVM Migrating a Veritas Volume Manager diskgroup from a physical environment to a virtual environment (P2V) Advantages of using a VMHost-based Storage Foundation stack

8 Veritas Storage Foundation and High Availability Solutions Support for HP-UX Integrity Virtual Machines Introduction Limitations with SF on VMGuests Limitations with SF on VMHosts Limitations with VCS on VMGuests Introduction This document provides information about support for HP Integrity Virtual Machines (IVMs) with Veritas Storage Foundation and High Availability Solutions. Review this entire document before installing your Veritas Storage Foundation and High Availability products in an HP IVM environment. For information about the Veritas Storage Foundation and High Availability Solutions 5.0.1 on HP-UX 11i v3, refer to the following documentation: Veritas Cluster Server Release Notes Veritas Storage Foundation Release Notes Veritas Storage Foundation Cluster File System Release Notes Veritas Cluster Server Installation Guide Veritas Storage Foundation Installation Guide Veritas Storage Foundation Cluster File System Installation Guide You can download the latest version of these guides from: http://sfdoccentral.symantec.com/storage_foundation_ha_501_hpux.html Note: Veritas Storage Foundation for Oracle RAC is not supported in an IVM environment. HP Integrity Virtual Machines terminology Table 1-1 describes the terminology that is helpful in configuring the Veritas software for HP Integrity Virtual Machines. Table 1-1 Term Attached I/O Terminology Definition A device given to a virtual machine without being virtualized by the VMHost.

Veritas Storage Foundation and High Availability Solutions Support for HP-UX Integrity Virtual Machines HP Integrity Virtual Machines terminology 9 Table 1-1 Term Shared I/O VMGuest VMHost VM-PM PM-PM VM-VM Backing store Terminology (continued) Definition A device on the VMHost that is virtualized and shared among different VMGuests. A virtual machine with its own operating system, resources, and identity within a physical host. An HP Integrity Server that has virtual machines running within it. It hosts the IVM package. A Veritas Cluster Server (VCS) supported configuration in which a cluster is formed among the VMGuests and physical machines. A VCS supported configuration in which a cluster is formed among the VMHosts and is used to manage VMGuests. A VCS supported configuration in which a cluster is formed among the VMGuests. A device on the VMHost, such as a network adapter, disk, or file that is allocated to the VMGuests. Online VM guest migration VSwitch Virtual Disk Virtual LvDisk Virtual FileDisk Accelerated Virtual I/O (AVIO) A technology to migrate a running VMGuest and its applications from one VMHost to another without service interruption. A network switch emulated in software that enables and controls network connections between the VMGuests and physical networks. An emulated SCSI disk whose virtual media comes from a VM Host disk LUN. An emulated SCSI disk whose virtual media is provided by a raw VM Host VxVM volume. An emulated SCSI disk whose virtual media comes from a VM Host file. This new technology from HP delivers a streamlined I/O path for both storage and networking resulting in significant performance improvements for I/O workloads in an IVM environment. VCS supports both AVIO and VIO configurations for storage and networking devices in an IVM environment.

10 Veritas Storage Foundation and High Availability Solutions Support for HP-UX Integrity Virtual Machines About HP Integrity Virtual Machines About HP Integrity Virtual Machines HP Integrity Virtual Machines (IVMs) is a hosted hypervisor virtualization technology within the HP Virtual Server Environment, which lets you create multiple virtual servers with shared resources within a single HP Integrity server or npartition. Figure 1-1 HP Integrity Virtual Machines architecture As shown in Figure 1-1, a virtual machine (VMGuest) runs within the physical machine (VMHost). The virtual machine is connected to a virtual storage device and a virtual switch (VSwitch). For more information about virtual switches, virtual storage devices, and Integrity Virtual Machines, refer to the HP documentation.

Veritas Storage Foundation and High Availability Solutions Support for HP-UX Integrity Virtual Machines Supported Storage Foundation and HP IVM versions 11 Supported Storage Foundation and HP IVM versions Table 1-2 describes the supported Storage Foundation (SF) and HP IVM versions. Table 1-2 Supported SF and HP IVM versions VMHost OS SF on VMHost IVM version VMGuest OS SF on VMGuest HP-UX 11i v2 5.0 MP2 3.5 HP-UX 11i v2 5.0 MP2 3.5 HP-UX 11i v3 March 2009 and later 5.0, 5.0.1 HP-UX 11i v3 5.0.1 4.0 HP-UX 11i v2 5.0 MP2 4.0 HP-UX 11i v3 March 2009 and later 5.0, 5.0.1 4.1 HP-UX 11i v2 5.0 MP2 4.1 HP-UX 11i v3 March 2009 and later 5.0, 5.0.1 4.2 HP-UX 11i v2 5.0 MP2 4.2 HP-UX 11i v3 March 2010 5.0, 5.0.1 Note: HP IVM 4.2 is certified with Veritas Storage Foundation 5.0.1 Rolling Patch 2. Supported VCS and IVM versions Table 1-3 describes the supported VCS and IVM versions on the host and guest systems.

12 Veritas Storage Foundation and High Availability Solutions Support for HP-UX Integrity Virtual Machines Supported VCS and IVM versions Table 1-3 Supported VCS and IVM versions VCS version Integrity VM version Host OS version Guest OS version Supported configuration 5.0.1 on HP-UX 11i v3 4.0 HP-UX 11i v3 September 2008 HP-UX 11i v2 HP-UX 11i v3 VM-VM See Cluster among VMGuests (VM-VM) on page 17. VM-PM See Cluster among VMGuests and physical machines (VM-PM) on page 21. PM-PM See Cluster among VMHosts (PM-PM) on page 24. 5.0.1 on HP-UX 11i v3 4.1 HP-UX 11i v3 March 2009 HP-UX 11i v2 HP-UX 11i v3 VM-VM See Cluster among VMGuests (VM-VM) on page 17. VM-PM See Cluster among VMGuests and physical machines (VM-PM) on page 21. PM-PM See Cluster among VMHosts (PM-PM) on page 24.

Veritas Storage Foundation and High Availability Solutions Support for HP-UX Integrity Virtual Machines Supported configurations using IVM 13 Table 1-3 Supported VCS and IVM versions (continued) VCS version Integrity VM version Host OS version Guest OS version Supported configuration 5.0.1 on HP-UX 11i v3 4.2 HP-UX 11i v3 March 2010 HP-UX 11i v2 HP-UX 11i v3 VM-VM See Cluster among VMGuests (VM-VM) on page 17. VM-PM See Cluster among VMGuests and physical machines (VM-PM) on page 21. PM-PM See Cluster among VMHosts (PM-PM) on page 24. Note: HP IVM 4.2 is certified with Veritas Cluster Server 5.0.1 Rolling Patch 2. Supported configurations using IVM Storage Foundation and High Availability supports various combinations of physical machines (VMHost) and virtual machines (VMGuest) running within the physical machines. You can install Veritas Storage Foundation and High Availability Solutions and Veritas Storage Foundation Cluster File System (SFCFS) either on the VMHost or on the VMGuest or on both. VMGuests, support both single-node and multiple-node high availability configurations. Table 1-4 shows the support matrix for the various deployment models.

14 Veritas Storage Foundation and High Availability Solutions Support for HP-UX Integrity Virtual Machines Storage Foundation supported configurations using IVM Table 1-4 Supported configurations using IVM Deployment on the VMGuest SF on VMGuest SFHA on VMGuest SFCFS on VMGuest SF not installed on VMGuest SF on VMHost Supported See Figure 1-4 on page 16. Not Supported Not Supported Supported See Figure 1-3 on page 16. Deployment on the VMHost/ backend device SFHA on VMHost SFCFS on VMHost Supported See Figure 1-16 on page 26. Not Supported Not Supported Not Supported Not Supported Not Supported Supported See Figure 1-15 on page 26. Not Supported Whole Disk on VMHost (SF is not used) Supported See Figure 1-2 on page 15. Supported * See Figure 1-9 on page 20. Supported * See Figure 1-17 on page 28. Not applicable Warning: * Indicates that these configurations are supported with fencing disabled. The following sections describe the deployment models for SF, SFHA, and SFCFS supported configurations using IVM. SF SFHA SFCFS See Storage Foundation supported configurations using IVM on page 14. See Storage Foundation High Availability supported configurations using IVM on page 17. See Storage Foundation Cluster File System supported configurations using IVM on page 27. Storage Foundation supported configurations using IVM Symantec recommends the following deployment models:

Veritas Storage Foundation and High Availability Solutions Support for HP-UX Integrity Virtual Machines Storage Foundation supported configurations using IVM 15 SF on VMGuest only SF on VMHost only SF on both VMGuest and VMHost See SF on VMGuest only on page 15. See SF on VMHost only on page 15. See SF on both VMGuest and VMHost on page 16. SF on VMGuest only Figure 1-2 shows a deployment in which SF is installed on the VMGuest and whole disk is exported to the VMGuest from the VMHost. Figure 1-2 SF on VMGuest only SF on VMHost only You can migrate the Volume Manager diskgroup from the physical environment to the virtual environment (P2V). See Migrating a Veritas Volume Manager diskgroup from a physical environment to a virtual environment (P2V) on page 28. Figure 1-3 shows a deployment in which SF is installed on the VMHost. The VMHost can export VxVM volumes or VxFS files as virtual disks to the VMGuest.

16 Veritas Storage Foundation and High Availability Solutions Support for HP-UX Integrity Virtual Machines Storage Foundation supported configurations using IVM Figure 1-3 SF on VMHost only SF on both VMGuest and VMHost Figure 1-4 shows a deployment in which SF is installed on both VMGuest and VMHost. The VMHost can export VxVM volumes or VxFS files as virtual disks to the VMGuest. Figure 1-4 SF on both VMGuest and VMHost

Veritas Storage Foundation and High Availability Solutions Support for HP-UX Integrity Virtual Machines Storage Foundation High Availability supported configurations using IVM 17 Storage Foundation High Availability supported configurations using IVM Storage Foundation High Availability (SFHA) supports the following configurations using IVM: Cluster among VMGuests (VM-VM) A cluster is formed among VMGuests. The VMGuests can be on the same VMHost or on different VMHosts. VCS is installed on the VMGuests. In this configuration, VCS manages the applications running within the VMGuests. See Cluster among VMGuests (VM-VM) on page 17. Note: For failover of VMGuests, refer to the PM-PM configuration. Cluster among VMGuests and physical machines (VM-PM) A cluster is formed among VMGuests and physical machines. VCS is installed on the VMGuests and physical machines. This configuration is a typical VCS application clustering. See Cluster among VMGuests and physical machines (VM-PM) on page 21. Cluster among VMHosts (PM-PM) The VMHosts form a cluster. In this configuration, VCS does not monitor applications running within VMGuests. See Cluster among VMHosts (PM-PM) on page 24. Cluster among VMGuests (VM-VM) The following configurations are supported: Cluster among VMGuests on two different VMHosts See Cluster among VMGuests on two different VMHosts on page 17. Cluster among VMGuests on the same VMHost See Cluster among VMGuests on the same VMHost on page 18. Cluster among VMGuests on two different VMHosts Figure 1-5 shows a configuration in which a cluster is formed between two VMGuests on different VMHosts.

18 Veritas Storage Foundation and High Availability Solutions Support for HP-UX Integrity Virtual Machines Storage Foundation High Availability supported configurations using IVM Figure 1-5 VCS cluster between VMGuests on two different VMHosts Cluster among VMGuests on the same VMHost Figure 1-6 shows a configuration in which a cluster is formed between two VMGuests on the same VMHost. This configuration is not generally recommended because it introduces a single point of failure. Figure 1-6 VCS cluster between VMGuests on the same VMHost Network configuration This section describes the network considerations for a VM-VM cluster. Figure 1-7 shows a cluster between VMGuest1 and VMGuest2.

Veritas Storage Foundation and High Availability Solutions Support for HP-UX Integrity Virtual Machines Storage Foundation High Availability supported configurations using IVM 19 Figure 1-7 Network configuration for a VM-VM cluster VMHost1 and VMHost2 have three physical network interface cards (NICs). lan0 is a public NIC, and lan1 and lan2 are private NICs. The private NICs of VMHost1 and VMHost2 are connected to each other through private heartbeat links. The network connections for VMGuest1 are as follows: A virtual switch VSwitch0 is mapped to the public physical NIC lan0 on VMHost1. A virtual NIC, NIC0 on VMGuest1, is connected to VSwitch0. A virtual switch VSwitch1 is mapped to the private physical NIC, lan1 on VMHost1. A virtual NIC named NIC1 on VMGuest1 is connected to VSwitch1. A virtual switch VSwitch2 is mapped to another private physical NIC lan2 on VMHost1. A virtual NIC named NIC2 is connected to VSwitch2. Set up public and private heartbeat network connections for VMGuest2 on the other node in a similar manner. The VSwitch names can be different on both the cluster nodes. Figure 1-8 shows the network configuration for multiple VMGuests.

20 Veritas Storage Foundation and High Availability Solutions Support for HP-UX Integrity Virtual Machines Storage Foundation High Availability supported configurations using IVM Figure 1-8 Cluster among multiple VMGuests Storage configuration Figure 1-9 shows a deployment in which SFHA is installed only on the VMGuest and whole disk is exported from the VMHost. Warning: Data corruption can occur because fencing is disabled. Figure 1-9 SFHA on the VMGuest only In this scenario, you can migrate the VxVM disk group from the physical environment to the virtual environment (P2V).

Veritas Storage Foundation and High Availability Solutions Support for HP-UX Integrity Virtual Machines Storage Foundation High Availability supported configurations using IVM 21 See Migrating a Veritas Volume Manager diskgroup from a physical environment to a virtual environment (P2V) on page 28. Setting up VMGuests for a VM-VM configuration Following is a high-level overview for setting up VMGuests. For detailed instructions, refer to HP documentation. To set up VMGuests Ensure that CPU and memory resources are available on the VMHosts. Install the HP Integrity VM package on the VMHosts. Create virtual switches to enable networking for VMGuests. Ensure that backing storage is available for VMGuests. Create VMGuests. Install the operating system in the VMGuests. Repeat the above steps for all the VMGuests in the cluster. Install VCS on all the VMGuests. For information about installing VCS, refer to the Veritas Cluster Server Installation Guide. Configure the resources that you want VCS to manage. If you intend to use the online VM guest migration feature, Symantec recommends that you set the VCS_GAB_TIMEOUT value in the /opt/vrtsvcs/bin/vcsenv file on all the VMGuests. This will prevent the VCS engine from missing heartbeats with GAB on a loaded system during migration. VCS_GAB_TIMEOUT=30000 export VCS_GAB_TIMEOUT Cluster among VMGuests and physical machines (VM-PM) Figure 1-10 shows a cluster between a VMGuest and a physical machine. VCS is installed on the virtual machine and the physical machine.

22 Veritas Storage Foundation and High Availability Solutions Support for HP-UX Integrity Virtual Machines Storage Foundation High Availability supported configurations using IVM Figure 1-10 A VM-PM cluster Note: Symantec recommends that physical machines should not host any virtual machines. Network configuration The network connection for the physical machine is similar to any other node in a VCS cluster. The VMGuest is connected to the physical machine through VSwitches and a physical NIC on its VMHost. Figure 1-11 shows the network configuration for a VM-PM configuration. Figure 1-11 Network configuration for a VM-PM configuration The network connections for the VMGuest are as follows: A virtual switch VSwitch0 is mapped to public physical NIC lan0 on VMHost. A virtual NIC, NIC0 on VMGuest is connected to VSwitch0.

Veritas Storage Foundation and High Availability Solutions Support for HP-UX Integrity Virtual Machines Storage Foundation High Availability supported configurations using IVM 23 A virtual switch Vswitch1 is mapped to the private NIC lan1 on VMHost. A virtual NIC, NIC1 on VMGuest is connected to VSwitch1. A virtual switch Vswitch2 is mapped to the private NIC lan2 on VMHost. A virtual NIC, NIC2 on VMGuest is connected to VSwitch2. Figure 1-12 shows the network configuration consisting of a physical machine and two VMGuests on the same VMHost. Figure 1-12 Network configuration for two VMGuests Storage configuration A raw disk backing store is supported for VMGuests in the VM-PM cluster. A whole disk can be provided to the virtual machine. If the disk contains a private disk group, it will also be visible from within the VMguest. Note: The VM-PM configuration does not support CVM backing stores. Setting up a VM-PM cluster Following are the high-level steps for setting up a VM-PM cluster. For detailed instructions, refer to HP documentation. To set up a VM-PM cluster Ensure that CPU and memory resources are available on the VMHosts. Install the HP Integrity VM package on the VMHosts.

24 Veritas Storage Foundation and High Availability Solutions Support for HP-UX Integrity Virtual Machines Storage Foundation High Availability supported configurations using IVM Create virtual switches to enable networking for VMGuests. Ensure that backing storage is available for VMGuests. Create the VMGuests. Install the operating system in the VMGuests. Repeat the above steps for all the VMGuests in the cluster. Install VCS on all the physical machines and VMGuests which are to be part of the cluster. For information about installing VCS, refer to the Veritas Cluster Server Installation Guide. Configure the resources that you want VCS to manage. Cluster among VMHosts (PM-PM) In this configuration, VCS manages a VMGuest as a resource. Figure 1-13 shows a VCS cluster between VMHost1 and VMHost2. Figure 1-13 A PM-PM configuration If the VMGuest on one of the VMHost faults, it is failed over to the other VMHost. For a successful failover of VMGuests across the VMHosts in a cluster, ensure that the VMGuests are configured consistently for the following attributes: VMGuest name VSwitch configuration Backing storage configuration The storage for the VMGuests must be accessible to all the VMHosts in the cluster.

Veritas Storage Foundation and High Availability Solutions Support for HP-UX Integrity Virtual Machines Storage Foundation High Availability supported configurations using IVM 25 VCS includes two new bundled agents, HPVirtualMachine agent and HPVSwitch agent. The HPVirtualMachine agent manages the VMGuests and the HPVSwitch agent manages the virtual switch. See Bundled agents for IVM to be used in a PM-PM configuration on page 27. Network and storage considerations The network configuration and storage configuration for the VMHosts is the same as the nodes in VCS cluster configurations. For information on configuring VCS, refer to the Veritas Cluster Server Installation and Configuration Guide. Figure 1-14 shows the network and storage organization for the PM-PM configuration. Figure 1-14 Network and storage organization for the PM-PM configuration Figure 1-15 shows a deployment in which SFHA is installed only on the VMHost and VxVM volume or VxFS files are exported to the VMGuest as Virtual disks. VCS monitors the virtual machines and their associated or dependent SF resources.

26 Veritas Storage Foundation and High Availability Solutions Support for HP-UX Integrity Virtual Machines Storage Foundation High Availability supported configurations using IVM Figure 1-15 SFHA on the VMHost only Figure 1-16 shows a configuration in which VMHosts form a VCS cluster and SF is installed in the VMGuest. VMHost can export a VxVM volume or VxFS file to the VMGuest. VCS monitors the VMGuests and its associated or dependent SF resources. Figure 1-16 SF on VMGuest and SFHA on VMHost VCS also supports a whole disk as a backing store to the VMGuest. The whole disk must be exported as a virtual disk to the VMGuest.

Veritas Storage Foundation and High Availability Solutions Support for HP-UX Integrity Virtual Machines Storage Foundation Cluster File System supported configurations using IVM 27 Setting up VMGuests for the PM-PM configuration Following is an overview for setting up the VMGuests. For detailed instructions, refer to HP documentation. To set up VMGuests Ensure that CPU and memory resources are available on the VMHosts. Install the HP Integrity VM package on the VMHosts. Create virtual switches to enable networking for VMGuests. Ensure that backing storage is available for VMGuests. Create VMGuests. The backing storage for the VMGuest must be accessible to all the VMHosts in the cluster. Configure the resources that you want VCS to manage. Bundled agents for IVM to be used in a PM-PM configuration The following agents are used to manage VMGuests running on VMHosts. HPVirtualMachine agent HPVSwitch agent Note: The HPVirtualMachine agent does not wait for the operating system to load completely. The agent reports the state of the resource as ONLINE immediately after the operating system starts booting. For information on these agents, refer to theveritas Cluster Server Bundled Agents Reference Guide. Storage Foundation Cluster File System supported configurations using IVM SFCFS on VMGuest only This section explains the deployment models for Veritas Storage Foundation Cluster File System. Figure 1-17 shows a deployment in which SFCFS is installed only on the VMGuest and the whole disk is exported from the VMHost.

28 Veritas Storage Foundation and High Availability Solutions Support for HP-UX Integrity Virtual Machines Migrating a Veritas Volume Manager diskgroup from a physical environment to a virtual environment (P2V) Warning: Data corruption can occur as fencing is disabled. Figure 1-17 SFCFS on VMGuest only You can migrate the Volume Manager diskgroup from the physical environment to the virtual environment (P2V). See Migrating a Veritas Volume Manager diskgroup from a physical environment to a virtual environment (P2V) on page 28. Migrating a Veritas Volume Manager diskgroup from a physical environment to a virtual environment (P2V) You can migrate the Veritas Volume Manager disk group from the physical environment to the virtual environment (P2V). Warning: If you use a Cross Platform Data Sharing (CDS) disk group on the physical server, you must migrate the data to a non-cds disk group. To execute the P2V migration: 1 Stop all the applications on the physical server. 2 Unmount any file systems which belong to the disk group that is being migrated. 3 Deport the disk group from the VMHost using the vxdg deport command: # vxdg deport dgname

Veritas Storage Foundation and High Availability Solutions Support for HP-UX Integrity Virtual Machines Advantages of using a VMHost-based Storage Foundation stack 29 4 Export all the disks which are a part of the disk group to the VMGuest. 5 Rescan the devices on the VMGuest using the following command # ioscan -fnc disk 6 Rescan the devices under Volume Manager using the following command # vxdisk scandisks 7 Import the disk group on the VMGuest using the vxdg import command: # vxdg import dgname 8 Mount the file systems which are part of the volumes in the diskgroup. 9 Start the applications on the VMGuest. Advantages of using a VMHost-based Storage Foundation stack DMP is centralized in the VMHost. As a result, the VMHost performs all the multipathing operations using DMP. The VMHost performs all the storage provisioning for the VMGuest using VxVM volumes and VxFS Files. Limitations with SF on VMGuests The Cross Platform Data Sharing (CDS) feature is enabled by default. The HP VMGuest does not support CDS. This restriction renders some of the CDS related features unusable. The CDS feature relies on SCSI mode sense data from the backend disk. HP IVM virtualizes the backend devices. As a result, the actual mode sense data is not available in the VMGuest. To create a VxVM disk group in the IVM environment, disable the CDS feature before creating a new diskgroup. To disable CDS, edit the /etc/default/vxdg file, and set the attribute-value pair cds=off. Alternatively, you can use the following command to set this attribute for a disk group: # vxdg -g diskgroup set cds=on off

30 Veritas Storage Foundation and High Availability Solutions Support for HP-UX Integrity Virtual Machines Limitations with SF on VMHosts Note: To migrate from a non-hp IVM environment to an HP IVM environment using CDS disk groups, migrate all the CDS disk groups to non-cds disk groups. This migration involves data movement. The VMGuest does not support the Enclosure Based Naming scheme (EBN) feature. As a result, some features like the following are not supported: Enclosure information is not available in the VMGuest. Therefore, all LUNs are claimed under the DISKS category. Mirroring across enclosures is also not supported. I/O Fencing is not supported in the VMGuest. CFS is only supported when fencing is disabled. I/O Fencing relies on SCSI-3 PGR support. HP IVM does not support SCSI-3 PGR in the VMGuest for virtualized disks. Symantec does not support a mixed CVM cluster configuration between VMGuest and another physical machine. For IVM version 3.5, the total length of the device identifier as supported by DMP in the VMGuest, is limited to 64 characters. When you export the VxVM volumes as backing stores from the VMHost to the VMGuest, the device identifier includes the VxVM volume path. In this case, the disk group and the volume name together cannot exceed 41 characters. When you export a VMHost Veritas File System (VxFS) file to the VMGuest, the length of the file path cannot exceed 54 characters. This length also includes the slash '/' characters. Limitations with SF on VMHosts VxFS drivers in the VMGuest cannot currently interact with the VxVM drivers in the VMHost. In such a configuration, some features like the following, which require direct VxVM-VxFS coordination, are rendered unusable: Before taking a data consistent snapshot of a VxVM volume containing a VxFS file system, you must shut down the application and unmount the filesystem. The resize operation on a filesystem on the VMGuest with an underlying device that is backed by a VxVM volume in the VMHost, has some restrictions. You must separately resize the VxVM volume and the filesystem in the VMGuest. The grow operation on a VxFS file system in the VMGuest with an underlying device that is backed by a VxVM volume, has restrictions. You must first grow the volume in the VMHost using the vxassist(1m) command.

Veritas Storage Foundation and High Availability Solutions Support for HP-UX Integrity Virtual Machines Limitations with VCS on VMGuests 31 You can then grow the file system in the VMGuest using the fsadm command. To shrink a VxFS file system, you should first shrink the file system in the VMGuest and then shrink the volume in the VMHost. To shrink the filesystem use the fsadm command. To shrink the volume, use the vxassist(1m) command. You cannot export a volume set to the VMGuest. SmartSync features functioning at the file-level are not supported. Limitations with VCS on VMGuests Controlling applications running within VMGuests is not supported in a PM-PM configuration. The VM-VM configuration does not manage VMGuests failovers as VCS is running within the VMGuests. I/O Fencing is not supported in the VMGuest.

32 Veritas Storage Foundation and High Availability Solutions Support for HP-UX Integrity Virtual Machines Limitations with VCS on VMGuests