Upgrade Guide Release 6.2 Rev A July 2013

Transcription

1 Upgrade Guide Release 6.2 Rev A July 2013

2 NOTICE The information contained in this document is subject to change without notice. UNLESS EXPRESSLY SET FORTH IN A WRITTEN AGREEMENT SIGNED BY AN AUTHORIZED REPRESENTATIVE OF STRATUS TECHNOLOGIES, STRATUS MAKES NO WARRANTY OR REPRESENTATION OF ANY KIND WITH RESPECT TO THE INFORMATION CONTAINED HEREIN, INCLUDING WARRANTY OF MERCHANTABILITY AND FITNESS FOR A PURPOSE. Stratus Technologies assumes no responsibility or obligation of any kind for any errors contained herein or in connection with the furnishing, performance, or use of this document. Software described in Stratus documents (a) is the property of Stratus Technologies Bermuda, Ltd. or the third party, (b) is furnished only under license, and (c) may be copied or used only as expressly permitted under the terms of the license. The software described in this document is covered by the following copyright: Stratus Technologies Bermuda, Ltd. 2008, Stratus documentation describes all supported features of the user interfaces and the application programming interfaces (API) developed by Stratus. Any undocumented features of these interfaces are intended solely for use by Stratus personnel and are subject to change without warning. This document is protected by copyright. All rights are reserved. Stratus Technologies grants you limited permission to download and print a reasonable number of copies of this document (or any portions thereof), without change, for your internal use only, provided you retain all copyright notices and other restrictive legends and/or notices appearing in the copied document. Stratus, the Stratus logo, ftserver, and the ftserver logo are registered trademarks of Stratus Technologies Bermuda, Ltd. The Stratus Technologies logo, the Stratus 24 x 7 logo, ActiveService, ftscalable, Automated Uptime, and Active Upgrade are trademarks of Stratus Technologies Bermuda, Ltd. The Application Availability Experts, ComputeThru, everrun, SplitSite, and are registered trademarks or trademarks of Stratus Technologies Bermuda, Ltd. Microsoft and Windows are registered trademarks of Microsoft Corporation in the United States and/or other countries; Xen and Citrix are registered trademarks and XenServer, XenCenter, and XenConvert are trademarks of Citrix Systems, Inc.; Java is a registered trademark of Sun Microsystems; Linux is a registered trademark of Linus Torvalds. Intel is a registered trademark of Intel Corporation. All other trademarks are the property of their respective owners.

3 Stratus everrun products are protected by one or more of the following patents: U.S. Patent Numbers: 5,600,784; 5,615,403; 5,787,485; 5,790,397; 5,896,523; 5,956,474; 5,983,371; 6,038,685; 6,205,565; 6,279,119; 6,473,869; 6,728,898; 7,373,545; 7,877,552. European Patent Numbers: EP ; EP ; EP ; EP ; EP ; EP ; EP ; EP ; GB ; Japanese Patent Numbers: ; ; Other patents pending. The product makes use of software covered under the GNU Public License (GPL) and the Lesser GNU Public License (LGPL). For a written copy of these licenses, see /var/ everrun/ current_everrun/licenses on any XenServer host on which everrun software is installed. Stratus will make source components available upon request, as required under the terms of the GPL. Contact everrun MX Support (US Toll-Free) or (International) Stratus Technologies Bermuda, Ltd. All rights reserved.

4 Contents Chapter 1 Introduction Overview...1 Upgrade Paths... 1 How to Use This Guide... 2 Terminology Used in this Guide... 2 Chapter 2 Upgrading everrun to 6.2 Upgrade Path... 5 Upgrade Requirements... 5 Advisory: Enable Multipathing on Fibre Channel Storage... 6 Before You Upgrade... 6 Downloading everrun MX - Release Creating the Upgrade Installation Media... 7 Obtaining the Required Licenses... 7 Installing the New Version of XenCenter... 8 Upgrading from everrun to everrun Starting the Upgrade... 9 Quorum Service Update (When Your Pool Includes Quorum) Installing XenServer Activating the XenServer License Installing the everrun 6.2 Software Completing the Upgrade of the Pool Upgrading Individual PVMs Contents iii

5 Chapter 3 Upgrading everrun to Overview...15 Upgrade Requirements...16 Additional Information about Device Driver Packages...17 Downloading the Software...17 Creating the Upgrade Installation Media...19 Phase 1 - Prepare the Pool for Upgrade...19 Phase 2 - Installing the everrun <version_id> Upgrade...22 Phase 3 - Updating Individual PVMs...24 Quorum Service Update (When Your Pool Includes Quorum)...24 Chapter 4 Upgrading everrun 6.0 to 6.1 Upgrade Path...25 Upgrade Requirements Advisory: Enable Multipathing on Fibre Channel Storage...26 Before You Upgrade Downloading everrun MX - Release Creating the Upgrade Installation Media...27 Obtaining the Required Licenses...27 Installing the New Version of XenCenter...28 Upgrading from everrun 6.0 to everrun Starting the Upgrade...29 Quorum Service Update (When Your Pool Includes Quorum) Installing XenServer 5.6 SP Activating the XenServer License Installing the everrun 6.1 Software...31 Completing the Upgrade of the Pool...33 Upgrading Individual PVMs...33 Chapter 5 Upgrading everrun to 6.0 Upgrade Path...37 Upgrade Requirements...38 Before You Upgrade...38 Downloading everrun MX - Release Creating the Upgrade Installation Media...40 iv Upgrade Guide

6 Obtaining and Installing the Required Licenses Updating Citrix XenCenter to Version Upgrading from everrun to everrun Starting the Upgrade Installing Citrix Security Hotfix XS55EU2001 (If Required) Installing the everrun 6.0 Software Launching the everrun Installer in Dom Completing the Upgrade of the Pool Quorum Service Update (When Required) Upgrading Individual PVMs Chapter 6 Upgrading everrun 5.1 to Upgrade Path Upgrade Requirements Before You Begin Upgrading from everrun 5.1 to everrun Upgrading the XenServer Master Host Preparing for the Upgrade Starting the Master Host Upgrade Updating Citrix XenCenter Using the Download Manager Installing Citrix Update 2 Using the Download Manager Verifying the Status of the Master Host Installing the everrun Upgrade Upgrading the XenServer Member Host Verifying the Status of the Master Host Upgrading the XenServer Software on the Member Host(s) Upgrading the everrun Software Verifying the Status of the Member Host Upgrading everrun PVMs Chapter 7 Upgrading everrun 5.0 to 5.1 Upgrade Path Upgrade Requirements Before You Begin Patch Existing PVMs Upgrade XenCenter Contents v

7 Upgrading from everrun 5.0 to everrun Upgrading the XenServer Master Host...62 Verifying the State of Pool Hosts and Protected VMs...62 Verifying Pool Readiness...62 Starting the Upgrade...63 Installing XenServer on the Master Host...64 Installing everrun 5.1 on the Master Host...64 Verifying the Upgrade of the Master Host...65 Upgrading the XenServer Member Host...66 Upgrading the XenServer Software...66 Installing the everrun 5.1 Software...66 Completing the Upgrade...67 Upgrading Individual PVMs...67 Appendix A Upgrading Quorum Service Software Overview...71 Upgrading the Quorum Service Software...71 System Preconditions...71 Performing the Upgrade...72 vi Upgrade Guide

8 Introduction 1 Overview This document explains how to apply the everrun software upgrade to your everrun configuration. Every everrun upgrade involves two separate procedures. Upgrade the software in the control domain (Dom0) on each XenServer host. Then you install the latest version of the everrun software and any specified updates to that software. After the everrun software has been upgraded, you can upgrade the software version used to protect the virtual machines. Upgrade Paths This guide contains instructions for multiple upgrade paths. For details on each upgrade, see the chapter indicated. From To Use everrun <version_id> running Citrix XenServer 5.6 Service Pack 2 with Hotfix 16 (XS56ESP2016) everrun 6.1 running Citrix XenServer 5.6 Service Pack 2 everrun 6.0 running XenServer 5.5 with Citrix Update 2 and Hotfix XS55EU2001, as well as XenCenter for Citrix 5.6 everrun 6.2 running Citrix XenServer with XS602E009, XS602E010, XS602E021, and XS602E023 everrun <version_id> running Citrix XenServer 5.6 Service Pack 2 with Hotfix 16 (XS56ESP2016) everrun 6.1 running Citrix XenServer 5.6 Service Pack 2, as well as XenCenter for Citrix 5.6 Service Pack 2. Chapter 2 Chapter 3 Chapter 4 Introduction 1

9 From To Use everrun running XenServer 5.5 with Citrix Update 2 (and, in some cases, Hotfix XS55EU2001) applied everrun 5.1 running XenServer 5.5 with no Citrix updates everrun 5.0 running on XenServer 5.0 with XenServer Hotfix 3 for XenServer 5.0 everrun 6.0 running XenServer 5.5 with Citrix Update 2 and Hotfix XS55EU2001, as well as XenCenter for Citrix 5.6 everrun running XenServer 5.5 with Citrix Update 2 Chapter 5 Chapter 6 everrun 5.1 running on XenServer Chapter 7 If you want to upgrade earlier versions of everrun, please consult the everrun Upgrade Guide at the everrun Customer Support web site for the release you want to install. How to Use This Guide Figure 1 on the following page summarizes everrun releases 5.0 and later, and indicates the allowed upgrade and rollback paths for each release. Each chapter contains a brief overview of the requirements for a specific upgrade, followed by details of that upgrade. Each chapter concludes by describing procedures for upgrading and unprotecting protected VMs (PVMs). Find the chapter that describes the update you want to perform, then follow the instructions in that chapter. Terminology Used in this Guide Both the everrun Configuration Planning Guide and the everrun Setup and Installation Guide contain a brief glossary of everrun and XenServer terminology used in the product documentation. A more extensive glossary is available in the everrun Online Help. 2 Upgrade Guide

10 Figure 1 everrun Upgrade Path Introduction 3

11 4 Upgrade Guide

12 Upgrading everrun to Upgrade Path This chapter describes the upgrade of two hosts running Citrix XenServer 5.6 Service Pack 2 (SP2) as well as everrun software. After the upgrade, the hosts will be running Citrix XenServer with XS602E009, XS602E010, XS602E021, and XS602E023, as well as everrun 6.2 software. NOTE: If you have questions about upgrading an alternative configuration supported in this release (for example, a pool with more than two hosts at a single location, or a two-host SplitSite pool where each server is at a different location), please consult everrun Technical Support. The process will involve two separate upgrades: The upgrade of the Citrix and everrun software in the XenServer control domain (Dom0), as described in the sections following Upgrading from everrun to everrun 6.2 on page 8. The upgrade of existing protected VMs (PVMs) to everrun 6.2, as described in the sections following Upgrading Individual PVMs on page 13. Upgrade Requirements The upgrade requires the following software and related documentation: Citrix XenServer everrun everrun MX Release 6.2 Several additional requirements are important to note: In this release, VMs cannot be protected with everrun unless they have XenServer Tools (paravirtualization or PV drivers) version Upgrading everrun to 6.2 5

13 Existing PVMs protected with everrun or earlier must be updated to PV driver version in order to support everrun 6.2. (PV drivers must be updated using the procedure described in Upgrading Individual PVMs on page 13.) A host that is updated to everrun 6.2 cannot be rolled back to everrun The upgrade process requires the shutdown of all PVMs and VMs in your pool. For that reason, the upgrade should be scheduled for a time when it is convenient to reboot all protected and unprotected VMs. Advisory: Enable Multipathing on Fibre Channel Storage If you are configuring fibre channel shared storage for your pool, It is strongly recommended that you enable multipathing on the storage repository. Without multipathing, guest VMs with a virtual disk image (VDI) configured on the associated FC SAN will not recover storage access properly following repair of a FC SAN until you restart the XenServer host. When multipathing is properly configured, you will avoid this problem. For more information, search the Citrix website for articles on multipathing, or contact everrun Technical Support. The everrun Setup and Installation Guide describes how to enable multipathing. Before You Upgrade Before you begin the upgrade, assemble the materials you ll need and perform all required pre-upgrade tasks. 1. Download the required product images and files, as well as relevant documentation, from the everrun website. 2. Create the installation media. 3. Obtain the required licenses and store them in an accessible directory on the management computer. You will activate the everrun 6.2 license as you upgrade. The following sections describe each of the pre-upgrade tasks. Downloading everrun MX - Release 6.2 The everrun web portal contains all the software required for the everrun MX Release 6.2 product. This section describes how to log in to the web portal and download the latest ISO images and documentation. The link to the portal is: Portal access is based on account: If you have an account, log in with your address and password. 6 Upgrade Guide

14 If you are in North America, call the Stratus Customer Assistance Center (CAC) at (800) or (800) , 24 hours a day, 7 days a week. Please have your everrun product license key available. To download the software: 1. Click the DOWNLOAD button at the top of the screen. 2. From the Select Product pull-down list, select everrun MX When the list of files displays, select the files you require for the upgrade. After selecting each file, click Save and choose a destination folder, then click Back to return to the pull-down list and make another selection. Starred files in the following list are required for the upgrade. - everrun MX 6.2 Product CD Image (ISO)* The software required to create the everrun installation CD. - Citrix XenServer 6.0.2, everrun Product CD Image (ISO)* The required XenServer software, which includes the software for the XenServer hosts as well as the XenCenter software for the management computer. - Citrix XenServer 6.0.2, Linux Guest Support CD Image (ISO) Optional for users who want to run Linux VMs. everrun does not support Linux guests. To download the documentation: 1. In the everrun MX product area, open the pull-down list and select Documentation Current Release. 2. Click everrun MX 6.2 Documentation Set to download the complete document set. Individual documents from the everrun and XenServer documentation set are also available for downloading. Always read the everrun Release Notes for the current release before beginning your upgrade. Install only the software specified in the everrun Release Notes. Creating the Upgrade Installation Media Use your company s standard processes to burn the product ISOs onto bootable CD- ROMs one or two for the Citrix ISOs, and another for the everrun ISO. Obtaining the Required Licenses Always obtain the licenses that support the version of the software to be installed. For this upgrade, you need the everrun 6.2 license. - The free Citrix license can be applied to each XenServer host using the procedure described in Activating the XenServer License on page 11. Upgrading everrun to 6.2 7

15 NOTE: The free XenServer license does not include XenServer High Availability (HA); this feature requires Citrix XenServer Advanced Edition or greater. For information on purchasing and installing this license, visit or contact your everrun representative. To install an Advanced Edition, you must use a Citrix license server as described in Licensing XenServer in the Citrix XenServer Installation Guide. - Early in the upgrade procedure, you will use the everrun Availability Center (eac) to install the everrun 6.2 license on the pool. Installing the New Version of XenCenter XenServer requires the new version of XenCenter you downloaded in the Citrix product ISO. You should install the new XenCenter software before you upgrade. To install the new version of XenCenter: Install the new XenCenter file on the management (client) computer. If a version of Citrix XenCenter is running on this computer, shut it down and use the Control Panel > Add or Remove Programs to remove this version. 1. On the management computer, locate the XenCenter installation file, XenCenter.msi, in the /client_install directory of the XenServer CD. Double-click the file to start the XenCenter Setup wizard. 2. Follow the onscreen process to install XenCenter on your client computer, then exit from the Setup wizard. 3. Start the new XenCenter on your client computer. You may see system alerts informing you that Updates or Hotfixes are available for download. Ignore any such messages and instead follow the process described in this chapter. Upgrading from everrun to everrun 6.2 This section describes all steps needed to upgrade both the master and member hosts to everrun 6.2 using the XenServer and everrun software. First you will install the XenServer software on the pool master host and all pool members. When you finish, you will install everrun on the master and member hosts. Starting the Upgrade The upgrade process involves a combination of tasks performed either in the everrun Availability Center (eac) or a command-line interface. For convenience, you can select 8 Upgrade Guide

16 a host in XenCenter and use the Console window to issue commands on that host, or you can use any remote console window connected to the host to issue the commands. To begin, make sure both XenCenter and the eac are open and connected to the pool you are upgrading. 1. First use the eac to make sure that no PVM mirror copies are in progress. If necessary, wait until all mirror copies have completed and PVMs are fully redundant before you begin the upgrade. 2. In the eac, select a pool icon from the Host tab and look at the Detail tab display to verify that the software version is a correct target for this upgrade. The current everrun version should be SP or a hotfix such as xxxx- HF. 3. Use the eac to install the everrun 6.2 license on the pool. 4. Next, click to display the list of hosts in the pool, and highlight each host until you locate a host that displays Server Type: Master on the Detail tab. 5. If XenServer HA is enabled on your pool, use the Console window to disable it: xe pool-ha-disable NOTE: If you have everrun quorum service enabled in your pool, pool failover is already set to manual, and you may see a message that it is already disabled. 6. From the same the command-line interface, disable everrun master failover on the pool: ev pool-master-failover-disable --force 7. Shut down all PVMs in the pool. ev pvm-shutdown --all --waitfor This will take a few moments to complete. 8. To verify that all PVMs are shut down, examine their power-state: ev pvm-list params=name-label,power-state The power-state for all PVMs should be halted. 9. To prevent PVMs from rebooting during the procedure, use the following command to list any PVMs that have the auto-power-on option enabled. The command saves the list of PVMs to a temporary file for use at the end of the procedure. mkdir /var/everrun/tmp Upgrading everrun to 6.2 9

17 ev pvm-list params=auto-power-on,name-label auto-power-on=true tee \ /var/everrun/tmp/auto_pvms.log If there are no PVMs that have auto-power-on enabled, skip this step. Otherwise issue the following command, specifying the pvm-uuid of each PVM you need to disable: ev pvm-param-set auto-power-on=false uuid=<pvm-uuid> 10. Use the eac or XenCenter to shut down any nonprotected VMs that may be running in the pool. 11. To verify that all VMs are shut down, examine their power-state: xe vm-list params=name-label,power-state is-control-domain=false The power-state for all VMs should be halted 12. To prevent VMs from rebooting during the procedure, use the following command to list any VMs that have the auto_poweron option enabled. The command saves the list of VMs to a temporary file for use at the end of the procedure. xe vm-list other-config:auto_poweron=true tee \ /var/everrun/tmp/auto_poweron_vms.log If no VMs had auto_poweron enabled, skip this step. Otherwise issue the following command, specifying the vm-uuid of each VM you need to disable: xe vm-param-set other-config:auto_poweron=false uuid=<vm-uuid> Quorum Service Update (When Your Pool Includes Quorum) If your configuration includes quorum service, make sure the current version of the quorum service software is installed on your pool s preferred and alternate quorum service computers while the PVMs and VMs on the host are shut down. If you have additional pools configured to use quorum service, be aware that PVMs in those pools can lose redundancy if any mistake occurs during the quorum upgrade. For more information and for quorum service installation procedures, see Appendix A: Upgrading Quorum Service Software on page 71 of this guide. Installing XenServer You ll start the software upgrade by shutting down the pool member host(s), then the pool master host. To install XenServer using a CD-ROM: 1. Before you install, shut down any pool member hosts, then shut down the pool master. 10 Upgrade Guide

18 2. Load the XenServer installation CD into the CD-ROM drive of the pool master host and power up the server. 3. Follow the onscreen instructions to install the XenServer software on the pool master. When offered a choice between a new installation and an upgrade installation, choose Upgrade. 4. When the installation is complete, reboot the master host NOTE: XenCenter will display an alert after upgrading XenServer software, "Failed to attach storage on server start...". This will be resolved during the everrun software installation and will not appear again. 5. Repeat the XenServer software installation on each pool member host, and reboot each host when the installation completes. NOTE: During the XenServer installation on member hosts, there may be a prompt that XenServer setup needs network access to continue and access your XenServer product repository. The eth number and MAC address of the management interface will be highlighted. Select "OK" to continue. The screens that follow will display the configuration details of the interface. DO NOT make any changes. Select OK for the upgrade to complete. NOTE: Do not restart any PVMs at this time. Instructions for restarting PVMs and VMs appear later in this upgrade process. Activating the XenServer License XenServer license activation is not required when upgrading from XenServer 5.6SP2 to XenServer The Stratus OEM license already in use correctly authorizes the new version of XenServer with the same features already in use. Installing the everrun 6.2 Software Now install the everrun software first on the master host and then on pool members hosts. The CD or shared directory contains everrun-6.2rlinstaller.bin, the everrun installer file. To execute this binary file in Dom0 on each XenServer host, you can mount the CD in a location that is accessible to Dom0, then use the host console in XenCenter to run the install binary. Upgrading everrun to

19 To run the everrun installer on the master host: 1. To create a mount point for the CD-ROM, issue the following command from the XenServer host console: mount -r /dev/cdrom /mnt 2. In a console window, run the everrun 6.2 installer file, everrun-6.2rlinstaller.bin, from the mount point: bash /mnt/everrun-6.2rl-installer.bin --install 3. Follow the onscreen instructions to complete the installation. If you need additional guidance, see the everrun Setup and Installation Guide, Chapter If you are installing everrun on the master host, disable master failover: ev pool-master-failover-disable --force 5. To allow the CD-ROM to be removed from the host, remove the mount point when you have finished installing the software on a host: umount /mnt 6. Reboot the master host. To run the everrun installer on the member host(s): 1. Use the commands shown in steps 1 to 3 above to install everrun 6.2 on each member host in the pool. 2. When a host installation is complete, use the command in step 5 above to unmount the CD-ROM, then reboot the host. 3. Repeat as needed until all pool hosts are upgraded. 4. After all hosts have been upgraded, reconnect the eac and XenCenter to the pool master host. If the eac was left running in a browser window during the upgrade process, close the window and restart the eac. Otherwise you may see errors when reconnecting. 5. Refer to the /var/everrun/tmp/auto_pvms.log file that saved a list of PVMs with the auto-power-on option enabled. If no PVMs were listed in the file, skip this step. Otherwise issue the following command, specifying the pvm-uuid of each PVM you want to re-enable. ev pvm-param-set auto-power-on=true uuid=<pvm-uuid> 6. Use the eac to start any PVMs that require a restart. 12 Upgrade Guide

20 NOTE: You may find it convenient to upgrade each PVM just after you restart it, using the procedure described in Upgrading Individual PVMs on page 13. Note that the PVM upgrade process includes an automatic PVM reboot. 7. Refer to the /var/everrun/tmp/auto_vms.log file that saved a list of VMs with the auto_poweron option enabled. If no VMs were listed in the file, skip this step. Otherwise issue the following command, specifying the vm-uuid of each VM you want to re-enable. xe vm-param-set other-config:auto_poweron=true uuid=<vm-uuid> Completing the Upgrade of the Pool 1. Return to the pool master host, and enable master failover: ev pool-master-failover-enable 2. Since the PVMs were shut down during the upgrade, it is unlikely that a mirror copy is required. However, it is a good idea to use the eac to check that all mirror copies are complete and that all PVMs are operational. 3. If you are using XenServer HA, re-enable it using XenCenter. 4. Use XenCenter or the eac to restart any VMs you shut down at the beginning of the upgrade. This completes your update of the XenServer and everrun host software. Continue with "Upgrading Individual PVMs, as soon as convenient. Upgrading Individual PVMs NOTE: Remember to upgrade a PVM only when it is convenient to reboot. The everrun PVM update utility updates the everrun software and the Citrix PV drivers. To update a PVM: 1. Mount the everrun installation CD-ROM on the Windows management client and set up to share it with the Windows PVM. NOTE: If you extracted the ISO contents to a directory on the Windows management computer, use the installation file stored in that directory, not the CD-ROM. Upgrading everrun to

21 2. Log in to the Administrator account and access the remotely mounted CD-ROM. 3. Copy the upgrade kit Update_PVM_6.2RL.exe from the everrun CD-ROM and run it locally. When you run the update program, a Welcome screen tells you: that the update kit requires Citrix XS Tools version (the Citrix paravirtualization or PV drivers). that the everrun installation package contains the required XS Tools kit and will start it during the upgrade process. that the PVM will reboot automatically at the end of the installation. NOTE: The XS Tools installation requires Microsoft.NET support. The everrun installation package contains the.net kit and will start during the upgrade process. NOTE: On Windows Server 2003 systems, Microsoft.NET requires the Windows Imaging Component (WIC). This must be installed before the everrun upgrade will run on Windows 2003 PVMs. 4. Click OK to open the Setup wizard, then click Next if you want to continue. 5. Click Install on the Ready to Install screen, and let the wizard run to completion. 6. Click OK to display the license agreement; read/accept the license and click Next. 7. Browse if you need to select a new install location, then click Install. As the wizard runs, you may see a pop-up screen with the following message: The Citrix network adapter driver has been replaced with everrun Ethernet redirectors. This is not a problem. Allow the XenServer Tools installation to run to completion, but do not select the option to reboot now. 8. At the end of the process, choose I want to manually reboot later. When the installation is complete, the PVM reboots. After all PVMs have been upgraded, the installation is complete. You do not have to log in to a PVM to complete its upgrade. 14 Upgrade Guide

22 Upgrading everrun to Overview This chapter describes the upgrade procedure for installing everrun on XenServer hosts running Citrix XenServer 5.6 SP2 and everrun (or subsequent everrun 6.1.0HF hotfix) software. Following upgrade, the hosts will be running the new version of everrun software with Citrix XenServer 5.6 SP2 Hotfix 16 (XS56ESP2016) applied to each host in the pool. NOTE: If you have questions concerning upgrade of an alternative configuration supported in this release (for example, a two-host SplitSite pool where each server is located at a different location), please consult everrun Technical Support. This software upgrade is a three phase procedure. Phases 1 and 2 are performed first on the master host, and then performed on each individual member host. After the pool has been completely upgraded, the third phase can be performed to apply the upgrade to each everrun protected VM. 1. The first phase begins by performing the initial steps that prepare the pool for installation of the new software. The software updates are downloaded and media required for the installation is prepared. If the host has hardware device drivers that must be updated for compatibility with Citrix XenServer 5.6 SP2 Hotfix 16, they will be installed during this phase. 2. The second phase upgrades the Citrix XenServer and everrun management software in the control domain (Dom0) of each host in the pool. The software is updated on each host independently, allowing you to keep everrun Protected VMs (PVM) running by moving them from a host that is currently being upgraded. VMs not protected with the everrun software must be live migrated to another host to continue running (if they have that capability). Upgrading everrun to

23 3. The third phase will upgrade the everrun software on individual PVMs. The PVM upgrade process should be scheduled for a time when it is convenient to reboot the PVM, which is automatically performed after it is upgraded. Detailed steps for each of these phases are provided in the following sections of this document. NOTE: Rollback to everrun capability is blocked. After the everrun installation process has applied Citrix Hotfix 16 (XS56ESP2016) to any host in the pool, rolling back to everrun is no longer possible. Upgrade Requirements The everrun installation utility will verify if all prerequisites are met prior to updating the host software. The following is required: Dom0 software prerequisites: Citrix XenServer 5.6 SP2 is installed (version ) everrun or everrun hotfix is installed XenSever Tools: The everrun 6.1.1<version_id> PVM software, like everrun 6.1.0, requires version of the Citrix XenServer Tools (paravirtualization or PV drivers). Therefore unprotected VMs cannot be protected unless the correct PV drivers are installed on the Windows VMs. Device driver packages: When everrun is installed on the host, Dom0 is running under Linux kernel version: xs xen After Citrix hotfix 16 and everrun 6.1.1<version_id> is installed, the host will be running a new kernel after the host has been rebooted. The new Linux kernel version will be: xs xen Since device drivers are built and installed to work with a specific Linux kernel, it is important to determine if new compatible device driver packages must be installed prior to installing everrun 6.1.1<version_id>. If new drivers are required but not installed and these drivers are required for booting the host, the old drivers will not function properly and therefore prevent the host from operating. Please refer to later sections of the Upgrade guide for detailed information. 16 Upgrade Guide

24 Additional Information about Device Driver Packages The Citrix XenServer installation disk installs device drivers for a wide variety of commonly installed hardware components. These device drivers have been built into or built to work directly with the Linux kernel that is shipped with a particular release of the XenServer software. As new hardware is developed and built into new servers, the Citrix XenServer installation disk for any given release of XenServer may not include device driver packages that supports the new hardware. To support new hardware components that are commonly available and integrated into server configurations, Citrix produces several special downloadable driver packages that can be installed either during a fresh/clean installation of the XenServer software or installed later onto an existing XenServer host. During a fresh or "bare-metal" installation of the XenServer software, the downloadable driver packages are burned to CD-ROM and referred to as "supplemental packs" or Driver Disks. They are installed when the XenServer installer prompts for "Supplemental Packs to install additional drivers". It may also be possible for driver packages to be installed on an existing XenServer host. The driver packages are installed by running a special installation script from a CLI window. The newly installed driver will not be used until after the host has been rebooted. Downloading the Software This section describes how to log in to the everrun Web Portal or customer web portal and download the latest software and documentation. The link to the portal is: Portal access is based on account:if you have an account, log in with your address and password. If you need assistance, call (Toll Free US and Canada) or Please have your everrun product license key available. To download the software: 1.Click the DOWNLOAD button at the top of the screen. 2.From the Select Product pull-down list, select everrun MX and Hot Fix Releases. 3..Click on the Read Me First download link and download the document. 4.Follow the instructions detailing the download process and details for upgrading from everrun version 6.1 to everrun version 6.1.1<version_id>. Upgrading everrun to

25 To download the Citrix Hotfix 16 compatible drivers if required: 1. Determine if new device driver packages are required for the host New drivers packages must be obtained and installed prior to the installation of everrun 6.1.1<version_id> if: A "Supplemental Pack" Driver Disk for Citrix XenServer 5.6 SP2 was previously downloaded from the Citrix website and installed during a bare-metal installation of XenServer on the host. The driver package for Citrix XenServer 5.6 SP2 was installed to support hardware that was added to the host after XenServer had been installed. To obtain replacement drivers from the Citrix website 1. Connect to the Citrix support web page ( to locate the drivers for XenServer 5.6 SP2 and search for links for driver disks for XenServer 5.6 SP2 Hotfix XS56ESP2002. The links will have the following format: Driver Disk for <vendor device description> - For XenServer 5.6 Service Pack 2 with Hotfix XS56ESP2002 NOTE: The example above references XS56ESP2002. The XenServer 5.6 SP2 Hotfix XS56ESP2016 package is a bundle of several hotfixes that include hotfixes XS56ESP2002, XS56ESP2005, XS56ESP2006, and XS56ESP2013 (i.e. hotfixes 2, 5, 6, 13, and 16). The link for the driver package, takes you to a web page for the driver package. 2. Review the information on the Citrix webpage The driver package web page provides a link to download the package, describes what the package is for, and provides a procedure outlining how the package is installed. 3. Download driver disk and extract contents Download the driver disk.zip file from the Citrix website. It contains the driver disk ISO file, driver source code, and MD5 checksum information for verifying the download. This should be unzipped to extract the driver disk ISO image. The source code file is not necessary for driver disk installation: it is provided to fulfill licensing obligations. Use the driver's ".iso.md5" file to verify that the download was successful. This checksum is of the ISO only, and can be verified by following the instructions at CTX116166: How to verify downloaded ISO images. 18 Upgrade Guide

26 Creating the Upgrade Installation Media NOTE: Use your company's standard processes to either extract files from ISO image files or for burning ISO image files to CD-ROM. Using the downloaded everrun product CD Image ISO file create the everrun <version_id> installation CD for the upgrade. - Burn separate CD-ROMs that include the contents of each ISO image OR - Extract the contents of the ISO images and update files to a shared folder that is accessible to the XenServer hosts. Included with the everrun software on the downloadable product ISO is Citrix Hotfix 16. It is located in the CitrixHotfixes folder. This folder must be present for applying the required Citrix hotfix and must reside in the same folder as the everrun installer when it is launched. NOTE: If additional device driver packages were downloaded, burning the ISO image file to CD-ROM is optional. Installing the driver packages from CD-ROM or directly from the ISO image file is described later in the procedure. Phase 1 - Prepare the Pool for Upgrade Always start upgrades on the pool master host. You will complete Phase 1 and Phase 2 on the master host. Then following the same steps, you will complete both Phase 1 and Phase 2 again, on each individual member host. Note that the steps will identify any differences in the procedure depending on whether the master host or member host is being upgraded. NOTE: The upgrade order is important. Follow the sequence described in this document to ensure a successful outcome 1. Make sure both XenCenter and the eac are open and connected to the pool you are upgrading. You can use the console window in XenCenter or a remote console window connected to the XenServer host to issue the command-line instructions. 2. Use the eac to make sure that no PVM mirror copies are in progress. If they are, wait until all mirror copies have completed and PVMs are fully redundant before you begin the upgrade. 3. Verify that the current server is the pool master or the pool member host that is being upgraded. Again, upgrade the pool master before any member hosts: Upgrading everrun to

27 ev host-list --localhost params=host-name,host-role NOTE: The information returned by this command will be useful for several steps during this procedure. The host uuid displayed will be used for the subsequent commands that require the "<xenserver_host_uuid>" parameter. 4. Perform this step if you are upgrading the master host otherwise this step can be skipped. Determine the source of failover of the pool master. Failover should be set to manual. If not, use the appropriate command from the following list to disable it: ev pool-param-get param-name=master-failover-via a. If master failover indicates everrun or manual, proceed to the next step. b. If master failover indicates platform, disable XenServer failover as follows: xe pool-ha-disable NOTE: If you have everrun quorum service is enabled in your pool, pool failover is already set to manual, and you may see a message that it is already disabled. 5. Perform this step if you are upgrading the master host otherwise this step can be skipped. Disable master failover on the pool: ev pool-master-failover-disable --force 6. Evacuate all PVMs to the other hosts: ev host-evacuate --waitfor --localhost This may take a minute. When evacuation is complete, the following message will be displayed: PVMs have been disabled on host: <host_uuid> 7. Issue the following command to verify that the evacuate process succeeded: ev pvm-list All PVMs listed should indicate evacuated for the state-host parameter on the host. 8. Using the information returned previously from the "ev host-list" output, specify the host uuid to migrate non-protected VMs that may be running on the host: xe host-evacuate uuid=<xenserver_host_uuid> 20 Upgrade Guide

28 9. Using XenCenter or using the following CLI command, verify that no VMs are running on the host. xe vm-list is-control-domain=false residenton=<xenserver_host_uuid> Log on to any VM that cannot be migrated and shut it down manually. 10. If new device driver packages compatible with Citrix hotfix 16 must be installed, use the steps that follow. As noted previously, it is critical to obtain device driver packages that are compatible with Citrix Hotfix 16 especially if they are required for booting the XenServer host. NOTE: Do not reboot the host until after the everrun upgrade installation has been completed on the host. The everrun installation takes place during phase 2 which follows in the next section. Make the driver package accessible to the XenServer host and install the driver If the driver ISO file was burned to CD-ROM, insert it into a drive that is accessible to Dom0. If it was not burned to CD-ROM, copy the driver disk ISO file directly to the XenServer host. The Citrix installation instructions recommend storing it in the /tmp directory. From a CLI window in Dom0, mount the driver disk and install the driver package. The mount command arguments will vary depending on whether the driver disk is still in ISO form, or was burned to CD-ROM. After the driver disk has been installed, do not reboot the host. Install each driver package that is required. For a CD-ROM, use: mkdir -p /mnt/tmp mount -r /dev/<path to cd-rom> /mnt/tmp cd /mnt/tmp/./install.sh cd / umount /mnt/tmp eject cdrom For an ISO file, use: mkdir -p /mnt/tmp mount /tmp/<path to ISO> /mnt/tmp -o loop,ro Upgrading everrun to

29 cd /mnt/tmp/./install.sh cd / umount /mnt/tmp Phase 2 - Installing the everrun <version_id> Upgrade 1. Make the everrun installation files accessible to the XenServer host. This can be done by mounting the media created by burning the everrun product ISO to CD- ROM or mounting the folder where the contents of the ISO kit were extracted to or by copying the files directly to a folder on the XenServer host. If the media was burned to a CD-ROM, create a mount point for the CD-ROM, issue the following command from the XenServer host console: mount -r /dev/cdrom /mnt Or if the files were extracted from the product ISO and a remote folder is shared from a Windows computer, issue a command similar to the following: mount -t cifs //<yourcomputername>/<sharedfoldername> /mnt -o user=<yourusername> 2. Examine the new mount point to guarantee that the everrun-6.1.1<version_id>installer.bin file and the CitrixHotfixes folder are present. ls -la /mnt 3. From a console window run the everrun installer file, everrun <version_id>-installer.bin from the mount point: bash /mnt/everrun-6.1.1<version_id>-installer.bin --install 4. Highlight OK and press Enter, then Press the Tab key so the scroll bar at right changes to red, scroll down and review the everrun License Agreement. Press the Tab key to highlight Accept and press Enter. 5. The next screen displays the Sun Java Runtime Environment license. Review the agreement, highlight Accept, and press Enter. 6. If Citrix Hotfix 16 must be applied to the pool, a popup will be displayed indicating that it is required. Highlight Continue and press Enter to allow the everrun installation to continue. 7. A confirmation popup will be displayed indicating that all verification steps have been completed. Highlight Continue and press Enter to complete the installation. No further interaction is required. If Citrix hotfix 16 must be applied, it will be uploaded and applied automatically by the installer. 22 Upgrade Guide

30 8. When the installation completes note any post installation reminders. The final screen provides the URL required to launch the browser-based everrun Availability Center (eac) console used to manage and monitor the everrun high availability environment. Record the URL for future reference. Press OK to close the Installer. 9. If you used a CD-ROM to install everrun type eject cdrom at the # prompt and press Enter to eject the media from the drive. If you used a mount point to install type unmount /mnt at the # prompt to remove the mount point. 10. Reboot the host using the following command: ev host-reboot --localhost NOTE: If this host is the master host, XenCenter and the eac are disconnected and unavailable until the master has finished rebooting. Restore the connection with the master host after it is running. 11. After the host reboot, it may take several minutes for VMs to be restarted and mirror copies to complete. Use eac to verify that PVMs are once again operational. 12. If the host that was just upgraded was a pool member host, VMs and PVMs that are primarily active on the host were migrated to a secondary host. You may wish to: use the eac to online migrate PVMs back to their primary host. use XenCenter to migrate non-protected VMs back to the host. 13. If necessary, use XenCenter to restart any non-protected VM that could not be migrated and had been manually shut down at the beginning of the host upgrade. 14. If more hosts in the pool must be upgraded, log in to the host and perform the procedures for phase 1 and phase 2 on that host. If all hosts in the pool have completed phase 1 and phase 2, perform the steps below to restore failover capabilities. a. Re-enable automatic failover of the pool master ev pool-master-failover-enable b. If you are using XenServer HA, re-enable it xe pool-ha-enable This completes Phase 2 update of the XenServer and everrun software. Proceed to Phase 3. Upgrading everrun to

31 Phase 3 - Updating Individual PVMs The everrun PVM update utility updates everrun on a PVM. The PVM will require network access to either a shared directory or a CD-ROM drive on the Windows management client to access the update software. Before you begin the PVM update procedure, consider the following: Because a PVM is rebooted automatically after the upgrade, schedule an upgrade only when it is convenient to reboot. To update a PVM: 1. Set up network share access to a directory or CD-ROM drive where the everrun upgrade kit can be accessed by the PVM. 2. Log in to the PVM's Administrator account and establish access the to shared directory or CD-ROM that contains the everrun update utility named Update_PVM_6.1.1<version_id>.exe. 3. Execute the PVM update program. Navigate to the shared location and double-click the Update_PVM_6.1.1<version_id>.exe file. OR Copy the update file Update_PVM_6.1.1<version_id>.exe to a local folder on the PVM and run it locally. 4. The installer Welcome screen tells you that: The PVM will reboot automatically at the end of the installation. 5. Click OK to open the Setup wizard, then click Next if you want to continue. 6. After all PVMs have been upgraded, the installation is complete. You do not have to log in to a PVM to complete the upgrade. Quorum Service Update (When Your Pool Includes Quorum) If your configuration includes quorum service, make sure the current version of the quorum service software is installed on your pool s preferred and alternate quorum service computers while the PVMs and VMs on the host are shut down. If you have additional pools configured to use quorum service, be aware that PVMs in those pools can lose redundancy if any mistake occurs during the quorum upgrade.. For more information and for quorum service installation procedures, see Appendix A: Upgrading Quorum Service Software on page 71 of this guide. 24 Upgrade Guide

32 Upgrading everrun 6.0 to Upgrade Path This chapter describes the upgrade of two hosts running Citrix XenServer 5.5 software with Update 2 as well as everrun 6.0 software. After the upgrade, the hosts will be running Citrix XenServer Service Pack 2 (SP2), as well as everrun 6.1 software. NOTE: If you have questions about upgrading an alternative configuration supported in this release (for example, a pool with more than two hosts at a single location, or a two-host SplitSite pool where each server is at a different location), please consult everrun Technical Support. The process will involve two separate upgrades: The upgrade of the Citrix and everrun software in the XenServer control domain (Dom0), as described in the sections following Upgrading from everrun 6.0 to everrun 6.1 on page 28. The upgrade of existing protected VMs (PVMs) to everrun 6.1, as described in the sections following Upgrading Individual PVMs on page 33. Upgrade Requirements The upgrade requires the following software and related documentation: Citrix XenServer 5.6 SP2 everrun everrun MX Release 6.1 Several additional requirements are important to note: In this release, VMs cannot be protected with everrun unless they have XenSever Tools (paravirtualization or PV drivers) version installed. Upgrading everrun 6.0 to