Unattended Installation on Windows Server 2003/2008

Save this PDF as:
 WORD  PNG  TXT  JPG

Size: px
Start display at page:

Download "Unattended Installation on Windows Server 2003/2008"

Transcription

1 Unattended Installation on Windows Server 2003/2008 vcenter Server Heartbeat 6.5 This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a new edition. To check for more recent editions of this document, see EN

2 Unattended Installation on Windows Server 2003/2008 You can find the most up-to-date technical documentation on the VMware Web site at: The VMware Web site also provides the latest product updates. If you have comments about this documentation, submit your feedback to: Copyright 2012 VMware, Inc. All rights reserved. This product is protected by U.S. and international copyright and intellectual property laws. VMware products are covered by one or more patents listed at VMware is a registered trademark or trademark of VMware, Inc. in the United States and/or other jurisdictions. All other marks and names mentioned herein may be trademarks of their respective companies. VMware, Inc Hillview Ave. Palo Alto, CA VMware, Inc.

3 Contents About This Book 5 1 Introduction 9 vcenter Server Heartbeat Concepts 9 Communications 10 vcenter Server Heartbeat Switchover and Failover Processes 12 2 Implementation 13 vcenter Server Heartbeat Implementation 13 Environmental Prerequisites 14 Pre-install Requirements 16 Server Deployment Architecture Options 17 Cloning Technology Options 18 Application Component Options 18 vcenter Deployment Models 21 vcenter Server Heartbeat Interoperability 22 Network Options 22 3 Unattended Installation of vcenter Server Heartbeat 29 Command Line Usage 29 Parameter File Elements 30 Unattended Setup of the Primary Server 33 Unattended Setup of a Virtual Secondary Server 34 Resulting IP Configuration 35 4 Post Installation Configuration 37 Post Installation Tasks 37 Configuring VirtualCenter Plug-in with the Correct Credentials 37 Registering the Heartbeat Plug-in Manually in vcenter 38 Configuring vcenter Server Heartbeat to Protect SQL Server 38 Configuring the Application Timeout Exception 40 Installing the View Composer Plug-in Post Installation 41 Upgrading vcenter Components 41 vcenter Server with SQL Server on a Separate Host 42 VMware, Inc. 3

4 Unattended Installation on Windows Server 2003/ Unattended Installation of vcenter Server Heartbeat Client Tools 43 6 Unattended Uninstall of vcenter Server Heartbeat 45 A Setup Error Messages 47 B Installation Verification Testing 49 Exercise 1 Auto-switchover 49 Exercise 2 - Data Verification 51 Exercise 3 - Switchover 52 C Upgrading 55 Upgrading vcenter Server Heartbeat 6.4 Update 1 to Upgrading vcenter Server 5.0 to 5.1 when SQL Database is Remote and vcenter Server Heartbeat is Installed 57 Upgrading vcenter Server 5.0 to 5.1 when SQL Database is Local and vcenter Server Heartbeat is Installed 62 Glossary 69 4 VMware, Inc.

5 About This Book The Installation Guide provides information about installing VMware vcenter Server Heartbeat when the Secondary server is virtual, including implementation in a Local Area Network (LAN) or Wide Area Network (WAN). To help you protect your VMware vcenter Server, this book provides an overview of installation procedures and guidance for configuring vcenter Server Heartbeat when performing an Unattended Installation. Intended Audience This guide assumes the reader has a working knowledge of networks including the configuration of TCP/IP protocols and domain administration, notably in Active Directory and DNS. VMware Technical Publications Glossary VMware Technical Publications provides a glossary of terms that might be unfamiliar to you. For definitions of terms as they are used in VMware technical documentation go to Overview of Content This guide is designed to give guidance on the installation and configuration of vcenter Server Heartbeat, and is organized into the following sections: Preface About This Book (this chapter) provides an overview of this guide and the conventions used throughout. Chapter 1 Introduction presents an overview of vcenter Server Heartbeat concepts including the Switchover and Failover processes. Chapter 2 vcenter Server Heartbeat Implementation discusses environmental prerequisites and common requirements for installation, options for server architecture, cloning technology, application components, and network configurations. It also gives guidance on anti-malware solutions, and provides a convenient summary of supported configurations as you perform the installation. Chapter 3 Unattended Installation of vcenter Server Heartbeat describes the installation process and guides you through installation on the Primary and Secondary servers when the Secondary server is virtual. Chapter 4 Post Installation Configuration provides the procedures to be performed after the installation of vcenter Server Heartbeat to configure specific components for operations. VMware, Inc. 5

6 Unattended Installation on Windows Server 2003/2008 Chapter 5 Unattended Installation of vcenter Server Heartbeat Client Tools describes the installation process to install Client Tools on a remote server using a command line procedure. Chapter 6 Unattended Uninstall of vcenter Server Heartbeat describes the uninstallation and removal of vcenter Server Heartbeat using a command line procedure. Appendix A Setup Error Messages lists error messages that may appear during setup and tests that will help you resolve the errors. Appendix B Installation Verification provides a procedure to verify that vcenter Server Heartbeat is properly installed and initially configured. Appendix C Upgrading provides the procedures necessary to upgrade vcenter Server Heartbeat and vcenter Server and its components from the previous version to the current version. Document Feedback VMware welcomes your suggestions for improving our documentation and invites you to send your feedback to Abbreviations Used in Figures Abbreviation Channel NIC P2V V2V Description VMware Channel Network Interface Card Physical to Virtual Virtual to Virtual Technical Support and Education Resources The following sections describe the technical support resources available to you. To access the current version of this book and other books, go to Online and Telephone Support Go to to use online support to submit technical support requests, view your product and contract information, and register your products. Go to to find out how to use telephone support for the fastest response on priority 1 issues (applies to customers with appropriate support contracts). Support Offerings Go to to find out how VMware support offerings can help meet your business needs. 6 VMware, Inc.

7 About This Book VMware Professional Services Go to to access information about education classes, certification programs, and consulting services. VMware Education Services courses offer extensive hands-on labs, case study examples, and course materials designed for use as on-the-job reference tools. Courses are available onsite, in the classroom, and live online. For onsite pilot programs and implementation best practices, VMware Consulting Services provides offerings to help you assess, plan, build, and manage your virtual environment. VMware, Inc. 7

8 Unattended Installation on Windows Server 2003/ VMware, Inc.

9 Introduction 1 vcenter Server Heartbeat is a Windows based service specifically designed to provide High Availability or Disaster Recovery protection for vcenter Server configurations without requiring any specialized hardware. This chapter includes the following topics: vcenter Server Heartbeat Concepts, on page 9 Communications, on page 10 vcenter Server Heartbeat Switchover and Failover Processes, on page 12 vcenter Server Heartbeat Concepts Architecture vcenter Server Heartbeat software is installed on a Primary (production) server and a Secondary (ready-standby) server. These names refer to the Identity of the servers and never change throughout the life of the server. Depending on the network environment, vcenter Server Heartbeat can be deployed in a Local Area Network (LAN) for High Availability or Wide Area Network (WAN) for Disaster Recovery, providing the flexibility necessary to address most network environments. When deployed, one of the servers performs the Role of the Active server that is visible on the Public network while the other is Passive and hidden from the Public network but remains as a ready-standby server. The Secondary server has a different Fully Qualified Domain Name (FQDN) different than the Primary server but uses the same file and data structure, same Principal (Public) network address, and can run all the same applications and services as the Primary server. Only one server can display the Principal (Public) IP address and be visible on the Public network at any given time. vcenter Server Heartbeat software is symmetrical in almost all respects, and either the Primary server or the Secondary server can take the active role and provide protected applications to the user. vcenter Server Heartbeat provides continuous access to the passive server simultaneously as the active server continues to service clients allowing the passive server to be easily accessed for maintenance purposes, updating anti-malware definition files, receiving operating system hot-fixes, updates and patches from third-party management software, and allows use of third-party monitoring tools. VMware, Inc. 9

10 Unattended Installation on Windows Server 2003/2008 Protection Levels vcenter Server Heartbeat provides the following protection levels: Server Protection provides continuous availability to end users through a hardware failure scenario or operating system crash. Additionally, vcenter Server Heartbeat protects the network identity of the production server, ensuring users are provided with a replica server on the failure of the production server. Network Protection proactively monitors the network by polling up to three nodes to ensure that the active server is visible on the network. Application Protection maintains the application environment ensuring that applications and services stay alive on the network. Performance Protection monitors system performance attributes to ensure that the system administrator is notified of problems and can take pre-emptive action to prevent an outage. Data Protection intercepts all data written by users and applications, and maintains a copy of this data on the passive server which can be used in the event of a failure. vcenter Server Heartbeat provides all five protection levels continuously, ensuring all facets of the user environment are maintained at all times, and that the Public network continues to operate through as many failure scenarios as possible. Communications vcenter Server Heartbeat communications consist of two crucial components, the VMware Channel and the Principal (Public) network. To accommodate communications requirements, vcenter Server Heartbeat can be configured to use either multiple NICs (1 X Channel and 1 X Principal (Public) connection) on each server providing a separate dedicated VMware Channel network from the Principal (Public) network or a single NIC on each server to fulfill both the VMware Channel and Principal (Public) network connection requirements. Figure 1-1. Communications Between Primary and Secondary Servers 10 VMware, Inc.

11 Chapter 1 Introduction VMware Channel The first component is the VMware Channel which provides communications between the active and passive servers. The VMware Channel is used for control and data transfer from the active server to the passive server and for monitoring of the active server's status by the passive server. The NICs on the active and passive servers used for the VMware Channel are normally configured with IP addresses outside of the Principal (Public) network subnet range and are referred to as the VMware Channel addresses. During installation, setup will disable NetBIOS for the VMware Channel(s) on the active and passive servers to prevent server name conflicts. The NICs that support connectivity across the VMware Channel can be standard 100BaseT Ethernet cards providing a throughput of 100 Mbits per second across standard Cat-5 cabling. When using multiple NICs providing a separate dedicated VMware Channel, this channel requires no hubs or routers, but the direct connection does require crossover cabling. When configured for a WAN deployment, configure the VMware Channel to use static routes over switches and routers to maintain continuous communications independent from corporate or public traffic. Principal (Public) Network The second component is the Principal (Public) network used by clients to connect to the active server. The Principal (Public) network provides access to the Principal (Public) IP address used by clients to connect to the active server and can be moved between the two Primary and Secondary servers to ensure clients can continue to connect to the active server in the event of a switchover or failover. The Principal (Public) IP address is a static IP address that is only available on the currently active server and is the IP address a client uses to connect to the active server. It must be configured as a static IP address, that is, not DHCP (Dynamic Host Configuration Protocol) enabled. In the figure above, the IP address is configured as The Principal (Public) IP address is always assigned to the active server in the pair and in the event of a switchover or failover, will be removed from the previously active server and reassigned to the new active server. The passive server will always have the Management IP address (discussed below)available and therefore provide access to the passive server. Management IP Address Both the Primary and Secondary servers are configured with Management IP addresses that allow access to the server when the server is in the passive role. The Management IP address is a static IP address in the same subnet as the Principal (Public) IP address and is always available for administrators to access the server. VMware, Inc. 11

12 Unattended Installation on Windows Server 2003/2008 vcenter Server Heartbeat Switchover and Failover Processes vcenter Server Heartbeat uses four different procedures managed switchover, automatic switchover, automatic failover, and managed failover to change the role of the active and passive servers depending on the status of the active server. Managed Switchover You can click Make Active on the vcenter Server Heartbeat Console Server: Summary page to manually initiate a managed switchover. When a managed switchover is triggered, the running of protected applications is transferred from the active machine to the passive machine in the server pair. The server roles are reversed. Automatic Switchover Automatic switchover (auto-switchover) is similar to failover (discussed in the next section) but is triggered automatically when system monitoring detects failure of a protected application. Automatic Failover Automatic failover is similar to automatic switchover (discussed above) but is triggered when the passive server detects that the active server is no longer running properly and assumes the role of the active server. Managed Failover Managed failover is similar to automatic failover in that the passive server automatically determines that the active server has failed and can warn the system administrator about the failure, but no failover actually occurs until the system administrator manually triggers this operation (the default configuration in a DR environment). 12 VMware, Inc.

13 Implementation 2 This chapter discusses the deployment options and prerequisites to successfully implement vcenter Server Heartbeat and provides a step-by-step process to assist in selecting options required for installation. The deployment scenario table at the end of this chapter provides a visual reference to configuration options supported by vcenter Server Heartbeat. This chapter includes the following topics: vcenter Server Heartbeat Implementation, on page 13 Environmental Prerequisites, on page 14 Pre-install Requirements, on page 16 Server Deployment Architecture Options, on page 17 Cloning Technology Options, on page 18 Application Component Options, on page 18 vcenter Deployment Models, on page 21 vcenter Server Heartbeat Interoperability, on page 22 Network Options, on page 22 vcenter Server Heartbeat Implementation vcenter Server Heartbeat is a versatile solution that provides complete protection of vcenter Server and SQL Server. It can be deployed in a LAN for high availability or across a WAN to provide disaster recovery. vcenter Server Heartbeat can protect vcenter Server and SQL Server installed on the same server, or protect vcenter Server in a distributed configuration. This flexibility enables vcenter Server Heartbeat to protect vcenter Server when using remote databases other than SQL Server. During the installation process, vcenter Server Heartbeat performs a variety of checks to ensure the server meets the minimum requirements for a successful installation. A critical stop or warning message appears if the server fails a check. Refer to the Appendix A, Setup Error Messages, on page 47 in this guide for a list of the checks and an explanation of the messages. You must resolve critical stops before you can proceed with setup. Prior to installing vcenter Server Heartbeat, select the deployment options you intend to use. The installation process will prompt you to select options throughout the procedure to create the configuration you want. VMware, Inc. 13

14 Unattended Installation on Windows Server 2003/2008 Environmental Prerequisites vcenter Server Heartbeat supports multiple versions of vcenter Server and its services. Supported Environments vcenter Server Heartbeat is supported on the following versions of Windows Server platforms Windows Server 2003 x86 Standard/Enterprise/Datacenter SP1 and SP2 Windows Server 2003 x64 Standard/Enterprise/Datacenter SP2 Windows Server 2003 R2 x64 Standard/Enterprise/Datacenter SP2 Windows Server 2008 x86 Standard/Enterprise/Datacenter SP1 and SP2 Windows Server 2008 x64 Standard/Enterprise/Datacenter SP1 and SP2 Windows Server 2008 R2 Standard/Enterprise/Datacenter SP1 Note vcenter Server Heartbeat supports protection of both standalone instances of vcenter Server and also when in Linked Mode groups. vcenter Server Heartbeat supports the following versions of vcenter Server vcenter Server 4.0 Update 1 vcenter Server 4.0 Update 2 vcenter Server 4.0 Update 3 vcenter Server 4.1 vcenter Server 4.1 Update 1 vcenter Server 5.0 vcenter Server 5.0 Update 1 vcenter Server VMware, Inc.

15 Chapter 2 Implementation vcenter Server Heartbeat supports the following versions of SQL Server on Windows Server platforms x86 Platform (32-bit hardware) SQL Server 2012 Standard, Enterprise, and Express Editions on Windows Server 2008 SP2 Standard and Enterprise SQL Server 2008 R2 Standard, Enterprise, and Express Editions on Windows Server 2008 SP2 Standard and Enterprise Windows Server 2003 SP2 Standard and Enterprise SQL Server 2008 Standard, Enterprise and Express Editions up to SP2 on Windows Server 2008 SP2 Standard and Enterprise Windows Server 2003 SP2 Standard and Enterprise SQL Server 2005 up to SP4 Standard, Enterprise, and Express Editions Windows Server 2008 SP2 Windows Server 2003 SP2 x64 / 64 Platform (64-bit hardware) SQL Server 2012 Standard, Enterprise, and Express Editions on Windows Server 2008 R2 SP1 Standard and Enterprise Windows Server 2008 SP2 Standard and Enterprise SQL Server 2008 R2 Standard, Enterprise, and Express Editions on Windows Server 2008 R2 Standard and Enterprise Windows Server 2008 SP2 Standard and Enterprise Windows Server 2003 SP2 Standard and Enterprise SQL Server 2008 Standard, Enterprise and Express Editions up to SP2 on Windows Server 2008 R2 Standard and Enterprise Windows Server 2008 SP2 Standard and Enterprise Windows Server 2003 SP2 Standard and Enterprise SQL Server 2005 up to SP4 Standard, Enterprise, and Express Editions Windows Server 2008 SP2 Windows Server 2003 SP2 Note This version of vcenter Server Heartbeat supports 32 bit versions of SQL Server 2005/2008 installed on x64 Operating Systems. VMware, Inc. 15

16 Unattended Installation on Windows Server 2003/2008 Unsupported Environments The following environments are not supported by vcenter Server Heartbeat On a server deployed as a Domain Controller (DC) On a server deployed as a Global Catalog Server On a server deployed as a DNS (Domain Name System) Server On an IA-64 Itanium Platform Pre-install Requirements Prior to installing vcenter Server Heartbeat, the following requirements must be met and are in addition to those required for vcenter Server and SQL Server. Verify that the Primary server is a member of the domain. The Domain for the Primary server will not change throughout the installation process although the Primary and Secondary server names will be changed as part of the installation procedure. vcenter Server Heartbeat only protects the vcenter Server and its components and SQL Server applications. Verify no other critical business applications are installed on the server. Verify that vcenter Guided Consolidation, vcenter Update Manager, vcenter Converter, ESXi Dump Collector, Syslog Collector, Auto Deploy, and Authentication Proxy are configured using Fully Qualified Domain Names (FQDN) rather than IP addresses. Verify that there is a minimum of 1GB of available RAM (2GB recommended) in addition to any other memory requirements for the Operating System or vcenter Server. Verify that a minimum 2GB of free disk space is available on the installation drive for vcenter Server Heartbeat. Obtain and use local administrator rights to perform vcenter Server Heartbeat installation. See knowledge base article Performing a Least Privilege Installation of vcenter Server Heartbeat. Verify that Microsoft.Net Framework 2.0 is installed prior to initiating Setup. If.Net Framework 2.0 is not installed, navigate to <kit location>\corekit\r2\dotnet and execute NetFx20SP2_<x86\x64>.exe to install.net Framework 2.0 before attempting to install vcenter Server Heartbeat. Apply the latest Microsoft security updates. All applications that will be protected by vcenter Server Heartbeat must be installed and configured on the Primary server prior to installing vcenter Server Heartbeat. Verify that both Primary and Secondary servers have identical system date, time, and time Zone settings. Verify that the Managed IP setting displayed in the Virtual Infrastructure Client is the same IP address used for the vcenter Server Heartbeat Principal (Public) IP address. If installing on Windows Server 2008, verify that Windows Server Backup Feature and Command Line Tools have been installed on the Primary and Secondary servers prior to installing vcenter Server Heartbeat. Installation of Windows Server Backup Feature and Command Line Tools will also install Windows PowerShell. 16 VMware, Inc.

17 Chapter 2 Implementation Verify that all services to be protected are running or set to Automatic prior to installation. During installation, protected services are set to manual to allow vcenter Server Heartbeat to start and stop services depending on the role of the server. The target state of the services is normally running on the active server and stopped on the passive. Configure Management IP addresses on the Principal (Public) NIC on both the Primary and Secondary servers. Note When installing on Windows Server 2008, adjacent IP addresses should be reserved and used for the Principal (Public) IP address and the Management IP addresses for the Primary and Secondary Servers. Server Deployment Architecture Options The selected server architecture affects the requirements for hardware and cloning of the Primary server. Note Unattended installation is supported only when using the Pre-Clone technique. Virtual to Virtual Virtual to Virtual is the supported architecture if vcenter Server is already installed on the production (Primary) server running on a virtual machine. Benefits to this architecture include reduced hardware cost, shorter installation time, and use of the Pre-Clone technique for installation. The Secondary virtual machine must meet the minimum requirements. The specifications of the Secondary virtual machine must match the specifications of the Primary virtual machine as follows: Similar CPU (including resource management settings) Memory configuration (including resource management settings) Appropriate resource pool priorities Each virtual machine used in the Virtual to Virtual pair must be on a separate ESX host to guard against failure at the host level. Important In a vsphere HA and DRS enabled cluster, set VM anti-affinity rules on the pair to ensure the VM's aren't placed on the same host to guard against failure at the host level. If using more than one NIC, each virtual NIC must use a separate virtual switch. VMware, Inc. 17

18 Unattended Installation on Windows Server 2003/2008 Physical to Virtual The Physical to Virtual architecture is used when the environment requires a mix of physical and virtual machines. This architecture is appropriate to avoid adding more physical servers or if you plan to migrate to virtual technologies over a period of time. The Secondary virtual machine must meet the minimum requirements. The specifications of the Secondary virtual machine must match the Primary physical server as follows: Similar CPU Identical Memory The Secondary virtual machine must have sufficient priority in resource management settings so that other virtual machines do not impact its performance. Each virtual NIC must use a separate virtual switch. Cloning Technology Options Cloning the Primary server to create a nearly identical Secondary server involves different technologies depending on the selected server architecture. Cloning Prior to Installation (Virtual Secondary) The following cloning technologies are supported for creating cloned images for use as a Secondary server before you begin installing vcenter Server Heartbeat: Use VMware vcenter Converter when cloning in a Physical to Virtual environment. Important When installing in a Physical to Virtual architecture, VMware Tools must not be installed on the Secondary server during the vcenter Server Heartbeat installation process. If VMware Tools are currently installed on the Secondary server, you must fully uninstall VMware Tools prior to initiation of the Setup process. Once the installation of vcenter Server Heartbeat has completed, you may reinstall VMware Tools. Use VMware vcenter virtual machine cloning when cloning in a Virtual to Virtual environment. Important When installing in a Virtual to Virtual architecture, VMware Tools must be installed and running on the Primary server before starting the vcenter Server Heartbeat installation process. Application Component Options vcenter Server Heartbeat can accommodate any of the supported vcenter Server configurations and protects the following services: 18 VMware, Inc.

19 Chapter 2 Implementation Supported vcenter Services vcenter Server Version 4.0 VMware vcenter Server VMware Guided Consolidation Service VMware License Server VMware ADAM VMware vcenter Management Web Server VMware vcenter Update Manager VMware vcenter Converter VMware vcenter Orchestrator Configuration VMware vcenter Orchestrator Server VMware vsphere Host Update Utility VMware vsphere Client VMware Mount Service for VirtualCenter vcenter Server Version 4.1 VMware vcenter Server VMware Guided Consolidation Service VMware License Sever VMware ADAM VMware vcenter Management Web Server VMware vcenter Update Manager VMware vcenter Converter VMware vcenter Orchestrator Configuration VMware vcenter Orchestrator Server VMware vsphere Host Update Utility VMware vsphere Client VMware Mount Service for VirtualCenter VMware, Inc. 19

20 Unattended Installation on Windows Server 2003/2008 vcenter Server Version 5.0 VMware vcenter Server VMware ADAM VMware vcenter Management Web Server VMware vcenter Update Manager VMware vcenter Orchestrator Configuration VMware vcenter Orchestrator Server VMware vsphere Host Update Utility VMware vsphere Client VMware Inventory Service VMware USB Arbitration Service VMware vsphere Web Client VMware vsphere ESXi Dump Collector VMware vsphere ESXi Dump Collector Web Server VMware vsphere Auto Deploy Waiter VMware vsphere Authentication Proxy VMware vsphere Authentication Proxy Adapter VMware Syslog Collector VMware vsphere Profile-Driven Storage Service 20 VMware, Inc.

21 Chapter 2 Implementation vcenter Server Versions 5.1 VMware vcenter Inventory Service VMware ADAM VMware USB Arbitration Service VMware vcenter Server VMware vsphere Client VMware vsphere Web Client VMware vcenter Update Manager VMware vsphere Update Manager Download Service VMware vcenter Orchestrator Configuration VMware vcenter Orchestrator Server VMware vsphere ESXi Dump Collector VMware Syslog Collector VMware vsphere Auto Deploy VMware vsphere Authentication Proxy VMware vcenter Host Agent Pre-Upgrade Checker VMware vcenter Single Sign On VMware vsphere Profile-Driven Storage Service RSA SSPI Service View Composer 1.1, 2.0, 2.7, and 3.0 Note Remote deployment of View Composer is supported starting with View Composer 3.0 VMware View Composer VMware Universal File Access vcenter Converter Enterprise Important Ensure that all VMware services are bound to the Principal (Public) IP address on the Principal (Public) network adapter. vcenter Deployment Models vcenter Server Heartbeat supports protection of vcenter Server in the following deployment models. vcenter Server with SQL Server on the Same Host To ensure adequate performance in 20+ host or 200+ virtual machine environments, VMware recommends that SQL Server and vcenter Server be installed on separate physical disk drives. VMDKs must be on separate datastores to avoid potential disk bottlenecks. VMware, Inc. 21

22 Unattended Installation on Windows Server 2003/2008 vcenter Server in a Distributed Environment In a distributed environment with remote services to be protected, vcenter Server Heartbeat must be installed for each distributed service at the service site. For example, when installing vcenter Server Heartbeat in an environment where SQL Server is on a separate host from vcenter Server, you must repeat the installation process for the Primary and Secondary server specifically for the SQL Server. vcenter Server Heartbeat Interoperability vcenter Server Heartbeat supports interoperability with multiple VMware technologies as indicated below. Linked Mode - vcenter Server Heartbeat supports protection of both Standalone instances of vcenter Server and Linked Mode groups. For more information about Linked Mode groups, see knowledge base article Joining or isolating a vcenter Server instance from a Linked Mode Group when protected by vcenter Server Heartbeat. vsphere HA/DR - vcenter Server Heartbeat supports High Availability for vcenter Server. For more information about configuring vsphere HA/DR, see the VMware vsphere Availability Guide. Site Recovery Manager (SRM) - Site Recovery Manager supports use of vcenter Server Heartbeat. For more information, see knowledge base article Using vcenter Heartbeat With SRM. Network Options Networking requirements are contingent upon how vcenter Server Heartbeat is deployed. To deploy as a High Availability (HA) solution, a LAN configuration is required. To deploy vcenter Server Heartbeat for Disaster Recovery (DR), a WAN configuration is required. Each network configuration has specific configuration requirements to ensure proper operation. vcenter Server Heartbeat can be configured to run using multiple NICs or a single NIC. Multiple NICs vcenter Server Heartbeat supports use of multiple NICs on each server pair. When using multiple NICs, one NIC is configured with the Principal (Public) IP address for client access and a Management IP address for administrator access while a second dedicated NIC is configured with the VMware Channel IP address. Deploying with multiple NICs provides the advantage of redundancy and also removes the risk of single point of failure that exists in single NIC configurations. To configure using multiple NICs on each server, see Multi-NIC Configuration. Note vcenter Server Heartbeat does NOT out-of-the-box support teams of NICs but can be configured to support teamed NICs with additional configuration steps when installing with teamed NICs present. See knowledge base article for more information about teamed NICs. Single NIC vcenter Server Heartbeat also supports use of a single NIC configured to perform all three functions, providing the Principal (Public) IP address to users, the Management IP address, and the VMware Channel for data transfer and control. To configure using a single NIC on each server, see Single NIC Configuration. 22 VMware, Inc.

23 Chapter 2 Implementation Local Area Network (LAN) When deployed in a LAN environment, vcenter Server Heartbeat requires that both servers use the same Principal (Public) IP address. Each server also requires a VMware Channel IP address and a Management IP address. Important vcenter Server Heartbeat will not attempt to update DNS and therefore, the Administrator must pre-populate the DNS server with entries for the new management names and IP addresses that are to be used. Wide Area Network (WAN) vcenter Server Heartbeat supports sites with different subnets. In this scenario, the Primary and Secondary server in the vcenter Server Heartbeat Pair will require unique Principal (Public) IP addresses in each subnet and a unique VMware Channel IP address in each subnet for each server. During Setup, select the Use different IP addresses for Secondary (Recommended for DR secondary) and specify the Principal (Public) IP addresses of both the Secondary server and the Primary server. vcenter Server Heartbeat also supports sites with the same subnet. In this scenario the vcenter Server Heartbeat shares a single Principal (Public) IP address between the Primary and Secondary server assigning it to the active server. Although the VMware Channel addresses should be unique within the same subnet. During Setup, select the Use same IP addresses for Secondary (Recommended for HA secondary) on the Principal (Public) IP Address Configuration page and specify the IP address to be shared by both servers. WAN Requirements WAN deployments require the following: Persistent static routing configured for the channel connection(s) where routing is required One NIC minimum, two NICs (1 x Public and 1 x Channel) are recommended At least one Domain Controller at the Disaster Recovery (DR) site VMware, Inc. 23

24 Unattended Installation on Windows Server 2003/2008 If the Primary and DR site uses the same subnet: During install, follow the steps for a LAN or VLAN on the same subnet Both servers in the vcenter Server Heartbeat pair use the same Public IP address If the Primary and DR site use different subnets: During install, follow the steps for a WAN Both servers in the vcenter Server Heartbeat pair require a separate Principal (Public) IP address and a VMware Channel IP address Provide a user account with rights to update DNS using the DNSUpdate.exe utility provided as a component of vcenter Server Heartbeat through vcenter Server Heartbeat Console Applications > Tasks > User Accounts VMware recommends integrating Microsoft DNS into AD so that DNSUpdate.exe can identify all DNS Servers that require updating At least one Domain Controller at the DR site Refer to the following articles in the VMware Knowledge Base: Knowledge base article Configuring DNS with VMware vcenter Server Heartbeat in a WAN Environment Knowledge base article Configuring vcenter Server Heartbeat to Update BIND9 DNS Servers Deployed in a WAN Bandwidth vcenter Server Heartbeat includes automatic bandwidth optimization in WAN environments. This feature compresses data transferred over the VMware Channel, optimizing the traffic for low bandwidth connections causing some additional CPU load on the active server. Determine the available bandwidth and estimate the required volume of data throughput to determine acceptable latency for the throughput. Additionally, the bandwidth can affect the required queue size to accommodate the estimated volume of data. VMware recommends making a minimum of 1Mbit of spare bandwidth available to vcenter Server Heartbeat. Latency Latency has a direct effect on data throughput. Latency on the link should not fall below the standard defined for a T1 connection. Heartbeat Diagnostics can assist in determining the available bandwidth, required bandwidth, and server workload. For more information about Heartbeat Diagnostics, contact VMware Professional Services. Network Interface Card (NIC) Configuration vcenter Server Heartbeat supports the use of both a single NIC or multiple NIC configuration on Primary and Secondary servers. The number of NICs present will determine how the NICs are configured. Important The Primary and Secondary servers must have the same number of NICs. 24 VMware, Inc.

25 Chapter 2 Implementation Multi-NIC Configuration When Using multiple NICs, one NIC functions for client and management access while a second NIC functions as a dedicated VMware Channel. Primary Server The Primary server is configured with the following connections: A Principal (Public) network connection configured with a static Principal (Public) IP address, network mask, gateway address, preferred DNS Server address, and secondary (if applicable) DNS server address. A Management IP connection using the same subnet and NIC as the Principal (Public) IP address, configured with a static IP address in the same subnet as the Principal (Public) IP address, network mask, gateway address, preferred DNS server address, and secondary (if applicable) DNS server address. VMware Channel connection(s) configured with a static IP address in a different subnet than the Principal (Public) IP address or Management IP address with a different IP address than the Secondary server channel NIC, and network mask. No gateway or DNS server address is configured. NetBIOS will be disabled during the installation process to prevent server name conflicts. The Register this connection's addresses in DNS check box must be cleared on all connections prior to installing vcenter Server Heartbeat. Secondary Server The Secondary server must have the same number of NICs as the Primary server and is configured as follows: Important Before running Setup on the Secondary Server, the Principal (Public) NIC providing the Principal (Public) and Management IP addresses, must be disconnected. The VMware Channel NIC must only be configured with the Channel IP address and the location of the Pre-sync data (backup folder) must be accessible via this IP address. A Principal (Public) connection configured with a static IP address, network mask, gateway address, preferred DNS server address, and secondary (if applicable) DNS server address. Note If deploying in a WAN, the Principal (Public) IP address of the Secondary server may be in a different subnet than the Primary server. A Management IP connection using the same subnet as the Secondary server's Principal (Public) IP address, configured using a static IP address, network mask, gateway address, preferred DNS server address, and secondary (if applicable) DNS server address. VMware Channel network connection(s) configured on a separate dedicated NIC with a static IP address in a different subnet than the Secondary Principal (Public) IP address or Management IP address and with a different IP address than the Primary server's VMware Channel NIC and a network mask. No gateway address or DNS server address is configured. NetBIOS will be disabled during the installation process to prevent server name conflicts. The Register this connection's addresses in DNS check box must be cleared on all connections prior to installing vcenter Server Heartbeat. VMware, Inc. 25

26 Unattended Installation on Windows Server 2003/2008 Single NIC Configuration Configuring vcenter Server Heartbeat using a single NIC requires that all three functions (Client access, Management access, and Channel operations) use the same physical or virtual NIC. Primary Server The Primary server requires a single NIC configured with the following IP addresses: A Principal (Public) IP address - configured using a static IP address, network mask, gateway address, preferred DNS server address, and secondary (if applicable) DNS server address. A Management IP address - configured on the same NIC as the Principal (Public) IP address with a unique static IP address in the same subnet as the Principal (Public) IP address, network mask, gateway address, preferred DNS server address, and secondary (if applicable) DNS server address. A VMware Channel IP address - configured on the same NIC as the Principal (Public) IP address and Management IP address, configured with a static IP address in the same or different subnet than the Principal (Public) IP address or Management IP address, and a network mask. No gateway address or DNS server address is configured. NetBIOS will be disabled during the installation process to prevent server name conflicts. The Register this connection's addresses in DNS check box must be cleared prior to installing vcenter Server Heartbeat. Secondary Server The Secondary server must have the same number of NICs as the Primary server and be configured as follows: Important Before running Setup on the Secondary Server, the single NIC must only be configured with the Channel IP address and the location of the Pre-sync data (backup folder) must be accessible via this IP address. A Management IP address - configured on the same NIC as the VMware Channel address with a unique static IP address in the same subnet as the Principal (Public) IP address, network mask, gateway address, preferred DNS server address, and secondary (if applicable) DNS server address. A VMware Channel IP address - configured on the same NIC as the Management IP address with a static IP address in the same or different subnet than the Management IP address, and the network mask. No gateway or DNS server address is configured. NetBIOS will be disabled during the installation process to prevent server name conflicts. The Register this connection's addresses in DNS check box must be cleared prior to installing vcenter Server Heartbeat. Firewall Configuration Requirements When firewalls are used to protect networks, you must configure them to allow traffic to pass through both the Client Connection port and the Default Channel port. 26 VMware, Inc.

27 Chapter 2 Implementation VMware recommends that the firewall be configured to allow the Client to connect to the Client Connection port by process, nfgui.exe, rather than by a specific port. To enable Channel communications between servers, configure the firewall to allow traffic to pass through on Port 57348, the Default Channel port. Important When installing on Windows Server 2008, Microsoft Windows may change the connection type from a Private network to an Unidentified network after you have configured the firewall port to allow channel communications resulting in the previously configured firewall changes to be reset for the new network type (Unidentified). The firewall rules must be recreated to allow traffic to pass through for the Client Connection port and the Default Channel port. VMware recommends that you change the Network List Manager Policy so that the VMware Channel network is identified as a Private Network, and not the default Unidentified Network. Anti-Malware Recommendations Consult with and implement the advice of your anti-malware provider, as VMware guidelines often follow these recommendations. Consult the VMware Knowledge Base for up to date information on specific anit-malware products. Do not use file level anti-malware to protect application server databases, such as MS SQL Server databases. The nature of database contents can cause false positives in malware detection, leading to failed database applications, data integrity errors, and performance degradation. VMware recommends that when implementing vcenter Server Heartbeat, you do not replicate file level anti-malware temp files using vcenter Server Heartbeat. The file level anti-malware software running on the Primary server must be the same as the software that runs on the Secondary server. In addition, the same file level anti-malware must run during both active and passive roles. Configure file level anti-malware to use the Management IP address on the passive server for malware definition updates. If this is not possible, manually update malware definitions on the passive server. Exclude the following VMware directories from file level anti-malware scans (C:\Program Files\VMware\VMware vcenter Server Heartbeat\ is the default installation directory): C:\Program Files\VMware\VMware vcenter Server Heartbeat\r2\logs C:\Program Files\VMware\VMware vcenter Server Heartbeat\r2\log Any configuration changes made to a file level anti-malware product on one server (such as exclusions) must be made on the other server as well. vcenter Server Heartbeat does not replicate this information. Deployment Options Summary Table 2-1 provides possible deployment options described in this section. VMware, Inc. 27

28 Unattended Installation on Windows Server 2003/2008 Table 2-1. Installation Options Deployment Architecture Network NICS Clone Technique Component LAN WAN Single Multiple Prior to Installation vcenter Server w/sql Local vcenter Server w/sql Remote vcenter Server Only Component Only Virtual to Virtual X X X X X X X X X Physical to Virtual X X X X X X X X X Note Installation using the Install Clone technique is not supported when performing Unattended Installations. 28 VMware, Inc.

29 Unattended Installation of vcenter Server Heartbeat 3 This chapter discusses the unattended installation process used to implement vcenter Server Heartbeat on Windows Server 2003 and Windows Server 2008 when the Secondary server is virtual. The installation process for all scenarios follows the same basic procedure. Unattended installation of vcenter Server Heartbeat requires use of command line options and a configuration parameters file. The configuration parameters file must be created prior to running the unattended installation to provide the configuration parameters for Setup and achieve your configuration goals. Note Unattended installation of vcenter Server Heartbeat is only supported when using the Pre-Clone technique and the Secondary server is virtual. Setup should only be run after verifying that the server (virtual or physical) has met all of the prerequisites listed in Pre-install Requirements, on page 16. Important Users should not cut-and-paste from this.pdf document but should type the actual commands and parameters. This chapter includes the following topics: Command Line Usage, on page 29 Parameter File Elements, on page 30 Unattended Setup of the Primary Server, on page 33 Unattended Setup of a Virtual Secondary Server, on page 34 Resulting IP Configuration, on page 35 Command Line Usage To perform an unattended installation, you must run the start /wait Setup command with the appropriate parameters from the command line. Additionally, you must create a.txt file (parameter file) that contains the information necessary to provide the intended options to the Setup application. The following information provides details about the parameters and parameter file necessary to successfully perform an unattended installation. start /wait Setup [-h] [-f<parameter file>] [-ni [-sp -se -sw -di]] [-DNSPassword:<password>] [-BACKUPPassword:<password>] VMware, Inc. 29

30 Unattended Installation on Windows Server 2003/2008 [-VCENTERPassword:<password>] [-ADMINPassword:<password>] [-secondaryinstall -uninstall -drvinstall ] Table 3-1. Command Line Parameters Parameter -h -f:<parameter file> -ni -sp -se -sw -di -DNSPassword:<password> -BACKUPPassword:<password> -VCENTERPassword:<password> -uninstall -ADMINPassword:<Password> -drvinstall -secondaryinstall Description Displays this usage information Uses a file of parameters to run Important If the file name/path contains any white space (space, tab) or special characters(-, /, etc.) then it must be enclosed in quotes "..." Not interactive, suppresses the Graphical User Interface. This instructs Setup not to use the Graphical User Interface. If this parameter is not specified but a parameter file is specified, the Graphical User Interface pages will be fully populated and require that the Next or Proceed button be clicked and any popup dialog boxes be acknowledged. Suppress Progress (Only for Non- interactive) Suppress Errors (Only for Non- interactive) Suppress Warnings (Only for Non- interactive) Display Info (Only for Non- interactive) The password used for DNSUpdate The password used for WBADMIN The password to use for vcenter Do not use unless instructed to do so The password to use for Administrator Do not use unless instructed to do so Do not use unless instructed to do so Important Only the DOS shell requires the "start /wait" Table 3-2. Return Codes Code Description : Success : Incorrect Usage (not enough parameters) : Invalid Parameter : File cannot be opened (file cannot be found) : File parse failed : Unable to Run (See output for specific problems) : Processing failed Parameter File Elements The parameter file is used to pass setup options to the Setup application and is made up a sequence of tagged lines, where the tag indicates what the data describes. 30 VMware, Inc.

Installation and Upgrade on Windows Server 2008/2012 When the Secondary Server is Physical VMware vcenter Server Heartbeat 6.6

Installation and Upgrade on Windows Server 2008/2012 When the Secondary Server is Physical VMware vcenter Server Heartbeat 6.6 Installation and Upgrade on Windows Server 2008/2012 When the Secondary Server is Physical VMware vcenter Server Heartbeat 6.6 This document supports the version of each product listed and supports all

More information

QuickStart Guide vcenter Server Heartbeat 5.5 Update 2

QuickStart Guide vcenter Server Heartbeat 5.5 Update 2 vcenter Server Heartbeat 5.5 Update 2 This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a new edition. To check for more recent

More information

Administrator Guide VMware vcenter Server Heartbeat 6.3 Update 1

Administrator Guide VMware vcenter Server Heartbeat 6.3 Update 1 Administrator Guide VMware vcenter Server Heartbeat 6.3 Update 1 This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a new edition.

More information

Installation Guide For Ipswitch Failover v9.0.1

Installation Guide For Ipswitch Failover v9.0.1 Installation Guide For Ipswitch Failover v9.0.1 Copyright 1991-2016 All rights reserved. This document, as well as the software described in it, is furnished under license and may be used or copied only

More information

Installing and Configuring vcenter Multi-Hypervisor Manager

Installing and Configuring vcenter Multi-Hypervisor Manager Installing and Configuring vcenter Multi-Hypervisor Manager vcenter Server 5.1 vcenter Multi-Hypervisor Manager 1.1 This document supports the version of each product listed and supports all subsequent

More information

Getting Started with ESXi Embedded

Getting Started with ESXi Embedded ESXi 4.1 Embedded vcenter Server 4.1 This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a new edition. To check for more recent

More information

Setup for Failover Clustering and Microsoft Cluster Service

Setup for Failover Clustering and Microsoft Cluster Service Setup for Failover Clustering and Microsoft Cluster Service ESX 4.0 ESXi 4.0 vcenter Server 4.0 This document supports the version of each product listed and supports all subsequent versions until the

More information

Installing and Configuring vcenter Support Assistant

Installing and Configuring vcenter Support Assistant Installing and Configuring vcenter Support Assistant vcenter Support Assistant 5.5 This document supports the version of each product listed and supports all subsequent versions until the document is replaced

More information

vsphere Upgrade vsphere 6.0 EN-001721-03

vsphere Upgrade vsphere 6.0 EN-001721-03 vsphere 6.0 This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a new edition. To check for more recent editions of this document,

More information

Setup for Failover Clustering and Microsoft Cluster Service

Setup for Failover Clustering and Microsoft Cluster Service Setup for Failover Clustering and Microsoft Cluster Service Update 1 ESX 4.0 ESXi 4.0 vcenter Server 4.0 This document supports the version of each product listed and supports all subsequent versions until

More information

Quick Start Guide For Ipswitch Failover v9.0

Quick Start Guide For Ipswitch Failover v9.0 For Ipswitch Failover v9.0 Copyright 1991-2015 All rights reserved. This document, as well as the software described in it, is furnished under license and may be used or copied only in accordance with

More information

Core Protection for Virtual Machines 1

Core Protection for Virtual Machines 1 Core Protection for Virtual Machines 1 Comprehensive Threat Protection for Virtual Environments. Installation Guide e Endpoint Security Trend Micro Incorporated reserves the right to make changes to this

More information

vsphere Upgrade Update 1 ESXi 6.0 vcenter Server 6.0 EN-001804-02

vsphere Upgrade Update 1 ESXi 6.0 vcenter Server 6.0 EN-001804-02 Update 1 ESXi 6.0 vcenter Server 6.0 This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a new edition. To check for more recent

More information

VMware Data Recovery. Administrator's Guide EN-000193-00

VMware Data Recovery. Administrator's Guide EN-000193-00 Administrator's Guide EN-000193-00 You can find the most up-to-date technical documentation on the VMware Web site at: http://www.vmware.com/support/ The VMware Web site also provides the latest product

More information

vsphere Replication for Disaster Recovery to Cloud

vsphere Replication for Disaster Recovery to Cloud vsphere Replication for Disaster Recovery to Cloud vsphere Replication 6.0 This document supports the version of each product listed and supports all subsequent versions until the document is replaced

More information

Reconfiguring VMware vsphere Update Manager

Reconfiguring VMware vsphere Update Manager Reconfiguring VMware vsphere Update Manager vsphere Update Manager 6.0 This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a

More information

vcenter Chargeback User s Guide

vcenter Chargeback User s Guide vcenter Chargeback 1.6 This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a new edition. To check for more recent editions

More information

Managing Multi-Hypervisor Environments with vcenter Server

Managing Multi-Hypervisor Environments with vcenter Server Managing Multi-Hypervisor Environments with vcenter Server vcenter Server 5.1 vcenter Multi-Hypervisor Manager 1.0 This document supports the version of each product listed and supports all subsequent

More information

vsphere Upgrade Guide

vsphere Upgrade Guide Update 1 ESX 4.0 ESXi 4.0 vcenter Server 4.0 vsphere Client 4.0 This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a new edition.

More information

VMware vcenter Discovered Machines Import Tool User's Guide Version 5.3.0.25 for vcenter Configuration Manager 5.3

VMware vcenter Discovered Machines Import Tool User's Guide Version 5.3.0.25 for vcenter Configuration Manager 5.3 VMware vcenter Discovered Machines Import Tool User's Guide Version 5.3.0.25 for vcenter Configuration Manager 5.3 This document supports the version of each product listed and supports all subsequent

More information

Migrating to vcloud Automation Center 6.1

Migrating to vcloud Automation Center 6.1 Migrating to vcloud Automation Center 6.1 vcloud Automation Center 6.1 This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a

More information

VMware vcenter Update Manager Administration Guide

VMware vcenter Update Manager Administration Guide VMware vcenter Update Manager Administration Guide Update 1 vcenter Update Manager 4.0 This document supports the version of each product listed and supports all subsequent versions until the document

More information

vsphere Replication for Disaster Recovery to Cloud

vsphere Replication for Disaster Recovery to Cloud vsphere Replication for Disaster Recovery to Cloud vsphere Replication 5.8 This document supports the version of each product listed and supports all subsequent versions until the document is replaced

More information

Setup for Failover Clustering and Microsoft Cluster Service

Setup for Failover Clustering and Microsoft Cluster Service Setup for Failover Clustering and Microsoft Cluster Service ESX 4.1 ESXi 4.1 vcenter Server 4.1 This document supports the version of each product listed and supports all subsequent versions until the

More information

Installing and Configuring vcloud Connector

Installing and Configuring vcloud Connector Installing and Configuring vcloud Connector vcloud Connector 2.7.0 This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a new

More information

vcenter Configuration Manager Backup and Disaster Recovery Guide VCM 5.3

vcenter Configuration Manager Backup and Disaster Recovery Guide VCM 5.3 vcenter Configuration Manager Backup and Disaster Recovery Guide VCM 5.3 This document supports the version of each product listed and supports all subsequent versions until the document is replaced by

More information

vrealize Operations Manager Customization and Administration Guide

vrealize Operations Manager Customization and Administration Guide vrealize Operations Manager Customization and Administration Guide vrealize Operations Manager 6.0.1 This document supports the version of each product listed and supports all subsequent versions until

More information

vsphere Networking ESXi 5.0 vcenter Server 5.0 EN-000599-01

vsphere Networking ESXi 5.0 vcenter Server 5.0 EN-000599-01 ESXi 5.0 vcenter Server 5.0 This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a new edition. To check for more recent editions

More information

Reconfiguring VMware vsphere Update Manager

Reconfiguring VMware vsphere Update Manager Reconfiguring VMware vsphere Update Manager vsphere Update Manager 5.5 This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a

More information

VMware vcenter Configuration Manager Backup and Disaster Recovery Guide vcenter Configuration Manager 5.4.1

VMware vcenter Configuration Manager Backup and Disaster Recovery Guide vcenter Configuration Manager 5.4.1 VMware vcenter Configuration Manager Backup and Disaster Recovery Guide vcenter Configuration Manager 5.4.1 This document supports the version of each product listed and supports all subsequent versions

More information

VMware vcloud Air Networking Guide

VMware vcloud Air Networking Guide vcloud Air This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a new edition. To check for more recent editions of this document,

More information

vsphere Host Profiles

vsphere Host Profiles ESXi 5.1 vcenter Server 5.1 This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a new edition. To check for more recent editions

More information

Installing and Administering VMware vsphere Update Manager

Installing and Administering VMware vsphere Update Manager Installing and Administering VMware vsphere Update Manager Update 1 vsphere Update Manager 5.1 This document supports the version of each product listed and supports all subsequent versions until the document

More information

Installing and Configuring vcenter Support Assistant

Installing and Configuring vcenter Support Assistant Installing and Configuring vcenter Support Assistant vcenter Support Assistant 6.0 This document supports the version of each product listed and supports all subsequent versions until the document is replaced

More information

Remote PC Guide Series - Volume 1

Remote PC Guide Series - Volume 1 Introduction and Planning for Remote PC Implementation with NETLAB+ Document Version: 2016-02-01 What is a remote PC and how does it work with NETLAB+? This educational guide will introduce the concepts

More information

RSA Authentication Manager 8.1 Setup and Configuration Guide. Revision 2

RSA Authentication Manager 8.1 Setup and Configuration Guide. Revision 2 RSA Authentication Manager 8.1 Setup and Configuration Guide Revision 2 Contact Information Go to the RSA corporate website for regional Customer Support telephone and fax numbers: www.emc.com/domains/rsa/index.htm

More information

Advanced Service Design

Advanced Service Design vcloud Automation Center 6.0 This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a new edition. To check for more recent editions

More information

vcenter Operations Manager for Horizon Supplement

vcenter Operations Manager for Horizon Supplement vcenter Operations Manager for Horizon Supplement vcenter Operations Manager for Horizon 1.6 This document supports the version of each product listed and supports all subsequent versions until the document

More information

Setup for Failover Clustering and Microsoft Cluster Service

Setup for Failover Clustering and Microsoft Cluster Service Setup for Failover Clustering and Microsoft Cluster Service Update 1 ESXi 5.1 vcenter Server 5.1 This document supports the version of each product listed and supports all subsequent versions until the

More information

Reconfiguring VMware vsphere Update Manager

Reconfiguring VMware vsphere Update Manager Reconfiguring VMware vsphere Update Manager vsphere Update Manager 6.0 This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a

More information

SolarWinds Failover Engine v6.7. Administrator's Guide

SolarWinds Failover Engine v6.7. Administrator's Guide SolarWinds Failover Engine v6.7 Administrator's Guide Administrator's Guide - SolarWinds Failover Engine Copyright 1995-2013 SolarWinds, Inc., all rights reserved worldwide. No part of this document may

More information

VMware vsphere 5.0 Evaluation Guide

VMware vsphere 5.0 Evaluation Guide VMware vsphere 5.0 Evaluation Guide Auto Deploy TECHNICAL WHITE PAPER Table of Contents About This Guide.... 4 System Requirements... 4 Hardware Requirements.... 4 Servers.... 4 Storage.... 4 Networking....

More information

Reconfiguration of VMware vcenter Update Manager

Reconfiguration of VMware vcenter Update Manager Reconfiguration of VMware vcenter Update Manager Update 1 vcenter Update Manager 4.1 This document supports the version of each product listed and supports all subsequent versions until the document is

More information

Whitepaper Continuous Availability Suite: Neverfail Solution Architecture

Whitepaper Continuous Availability Suite: Neverfail Solution Architecture Continuous Availability Suite: Neverfail s Continuous Availability Suite is at the core of every Neverfail solution. It provides a comprehensive software solution for High Availability (HA) and Disaster

More information

VMware vcenter Support Assistant 5.1.1

VMware vcenter Support Assistant 5.1.1 VMware vcenter.ga September 25, 2013 GA Last updated: September 24, 2013 Check for additions and updates to these release notes. RELEASE NOTES What s in the Release Notes The release notes cover the following

More information

Management Pack for vrealize Infrastructure Navigator

Management Pack for vrealize Infrastructure Navigator Management Pack for vrealize Infrastructure Navigator This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a new edition. To

More information

Installing and Configuring vcloud Connector

Installing and Configuring vcloud Connector Installing and Configuring vcloud Connector vcloud Connector 2.0.0 This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a new

More information

vsphere Networking ESXi 5.1 vcenter Server 5.1 EN

vsphere Networking ESXi 5.1 vcenter Server 5.1 EN ESXi 5.1 vcenter Server 5.1 This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a new edition. To check for more recent editions

More information

Quick Start Guide. for Installing vnios Software on. VMware Platforms

Quick Start Guide. for Installing vnios Software on. VMware Platforms Quick Start Guide for Installing vnios Software on VMware Platforms Copyright Statements 2010, Infoblox Inc. All rights reserved. The contents of this document may not be copied or duplicated in any form,

More information

VMware vcloud Automation Center 6.0

VMware vcloud Automation Center 6.0 VMware 6.0 Reference Architecture TECHNICAL WHITE PAPER Table of Contents Overview... 4 Initial Deployment Recommendations... 4 General Recommendations... 4... 4 Load Balancer Considerations... 4 Database

More information

Installing and Using the vnios Trial

Installing and Using the vnios Trial Installing and Using the vnios Trial The vnios Trial is a software package designed for efficient evaluation of the Infoblox vnios appliance platform. Providing the complete suite of DNS, DHCP and IPAM

More information

VMware vsphere Data Protection Evaluation Guide REVISED APRIL 2015

VMware vsphere Data Protection Evaluation Guide REVISED APRIL 2015 VMware vsphere Data Protection REVISED APRIL 2015 Table of Contents Introduction.... 3 Features and Benefits of vsphere Data Protection... 3 Requirements.... 4 Evaluation Workflow... 5 Overview.... 5 Evaluation

More information

Index C, D. Background Intelligent Transfer Service (BITS), 174, 191

Index C, D. Background Intelligent Transfer Service (BITS), 174, 191 Index A Active Directory Restore Mode (DSRM), 12 Application profile, 293 Availability sets configure possible and preferred owners, 282 283 creation, 279 281 guest cluster, 279 physical cluster, 279 virtual

More information

VMware vsphere Replication Administration

VMware vsphere Replication Administration VMware vsphere Replication Administration vsphere Replication 6.1 This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a new

More information

EMC Data Domain Management Center

EMC Data Domain Management Center EMC Data Domain Management Center Version 1.1 Initial Configuration Guide 302-000-071 REV 04 Copyright 2012-2015 EMC Corporation. All rights reserved. Published in USA. Published June, 2015 EMC believes

More information

vcloud Air - Virtual Private Cloud OnDemand Networking Guide

vcloud Air - Virtual Private Cloud OnDemand Networking Guide vcloud Air - Virtual Private Cloud OnDemand Networking Guide vcloud Air This document supports the version of each product listed and supports all subsequent versions until the document is replaced by

More information

RSA Authentication Manager 8.1 Virtual Appliance Getting Started

RSA Authentication Manager 8.1 Virtual Appliance Getting Started RSA Authentication Manager 8.1 Virtual Appliance Getting Started Thank you for purchasing RSA Authentication Manager 8.1, the world s leading two-factor authentication solution. This document provides

More information

Performance of VMware vcenter (VC) Operations in a ROBO Environment TECHNICAL WHITE PAPER

Performance of VMware vcenter (VC) Operations in a ROBO Environment TECHNICAL WHITE PAPER Performance of VMware vcenter (VC) Operations in a ROBO Environment TECHNICAL WHITE PAPER Introduction Many VMware customers have virtualized their ROBO (Remote Office Branch Office) offices in order to

More information

vsphere Networking vsphere 5.5 ESXi 5.5 vcenter Server 5.5 EN-001074-02

vsphere Networking vsphere 5.5 ESXi 5.5 vcenter Server 5.5 EN-001074-02 vsphere 5.5 ESXi 5.5 vcenter Server 5.5 This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a new edition. To check for more

More information

vrealize Air Compliance OVA Installation and Deployment Guide

vrealize Air Compliance OVA Installation and Deployment Guide vrealize Air Compliance OVA Installation and Deployment Guide 14 July 2015 vrealize Air Compliance This document supports the version of each product listed and supports all subsequent versions until the

More information

PHD Virtual Backup for Hyper-V

PHD Virtual Backup for Hyper-V PHD Virtual Backup for Hyper-V version 7.0 Installation & Getting Started Guide Document Release Date: December 18, 2013 www.phdvirtual.com PHDVB v7 for Hyper-V Legal Notices PHD Virtual Backup for Hyper-V

More information

Veeam Cloud Connect. Version 8.0. Administrator Guide

Veeam Cloud Connect. Version 8.0. Administrator Guide Veeam Cloud Connect Version 8.0 Administrator Guide April, 2015 2015 Veeam Software. All rights reserved. All trademarks are the property of their respective owners. No part of this publication may be

More information

VMware vcenter Configuration Manager and VMware vcenter Application Discovery Manager Integration Guide

VMware vcenter Configuration Manager and VMware vcenter Application Discovery Manager Integration Guide VMware vcenter Configuration Manager and VMware vcenter Application Discovery Manager Integration Guide vcenter Configuration Manager 5.6 vcenter Application Discovery Manager 6.2 This document supports

More information

VMware vcloud Air - Disaster Recovery User's Guide

VMware vcloud Air - Disaster Recovery User's Guide VMware vcloud Air - Disaster Recovery User's Guide vcloud Air This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a new edition.

More information

365 Evans Suite 300 Toronto, Ontario M8Z 1K2 Phone: Fax:

365 Evans Suite 300 Toronto, Ontario M8Z 1K2 Phone: Fax: Course: Virtualization with VMware ESX and VirtualCenter Description: Price: $2,895.00 Category: VMware Duration: 5 days Schedule: Request Dates Outline: This class is a 5-day (optional 4-day) intense

More information

VMware vsphere-6.0 Administration Training

VMware vsphere-6.0 Administration Training VMware vsphere-6.0 Administration Training Course Course Duration : 20 Days Class Duration : 3 hours per day (Including LAB Practical) Classroom Fee = 20,000 INR Online / Fast-Track Fee = 25,000 INR Fast

More information

vcenter Support Assistant User's Guide

vcenter Support Assistant User's Guide vcenter Support Assistant 5.5 This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a new edition. To check for more recent editions

More information

Virtual Appliance Setup Guide

Virtual Appliance Setup Guide The Virtual Appliance includes the same powerful technology and simple Web based user interface found on the Barracuda Web Application Firewall hardware appliance. It is designed for easy deployment on

More information

vsphere Networking vsphere 6.0 ESXi 6.0 vcenter Server 6.0 EN-001391-01

vsphere Networking vsphere 6.0 ESXi 6.0 vcenter Server 6.0 EN-001391-01 vsphere 6.0 ESXi 6.0 vcenter Server 6.0 This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a new edition. To check for more

More information

Technical Note. vsphere Deployment Worksheet on page 2. Express Configuration on page 3. Single VLAN Configuration on page 5

Technical Note. vsphere Deployment Worksheet on page 2. Express Configuration on page 3. Single VLAN Configuration on page 5 Technical Note The vfabric Data Director worksheets contained in this technical note are intended to help you plan your Data Director deployment. The worksheets include the following: vsphere Deployment

More information

VMware vcenter Configuration Manager Software Provisioning Components Installation and User Guide

VMware vcenter Configuration Manager Software Provisioning Components Installation and User Guide VMware vcenter Configuration Manager Software Provisioning Components Installation and User Guide Package Studio 1.1 Software Repository for Windows 1.1 Package Manager 1.2 This document supports the version

More information

Clearswift SECURE Exchange Gateway Installation & Setup Guide. Version 1.0

Clearswift SECURE Exchange Gateway Installation & Setup Guide. Version 1.0 Clearswift SECURE Exchange Gateway Installation & Setup Guide Version 1.0 Copyright Revision 1.0, December, 2013 Published by Clearswift Ltd. 1995 2013 Clearswift Ltd. All rights reserved. The materials

More information

VMware Identity Manager Connector Installation and Configuration

VMware Identity Manager Connector Installation and Configuration VMware Identity Manager Connector Installation and Configuration VMware Identity Manager This document supports the version of each product listed and supports all subsequent versions until the document

More information

HP CloudSystem Enterprise

HP CloudSystem Enterprise HP CloudSystem Enterprise F5 BIG-IP and Apache Load Balancing Reference Implementation Technical white paper Table of contents Introduction... 2 Background assumptions... 2 Overview... 2 Process steps...

More information

VMware vcloud Automation Center 6.1

VMware vcloud Automation Center 6.1 VMware vcloud Automation Center 6.1 Reference Architecture T E C H N I C A L W H I T E P A P E R Table of Contents Overview... 4 What s New... 4 Initial Deployment Recommendations... 4 General Recommendations...

More information

ESX Configuration Guide

ESX Configuration Guide ESX 4.0 vcenter Server 4.0 This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a new edition. To check for more recent editions

More information

WhatsUp Gold v16.3 Installation and Configuration Guide

WhatsUp Gold v16.3 Installation and Configuration Guide WhatsUp Gold v16.3 Installation and Configuration Guide Contents Installing and Configuring WhatsUp Gold using WhatsUp Setup Installation Overview... 1 Overview... 1 Security considerations... 2 Standard

More information

User Guide for VMware Adapter for SAP LVM VERSION 1.2

User Guide for VMware Adapter for SAP LVM VERSION 1.2 User Guide for VMware Adapter for SAP LVM VERSION 1.2 Table of Contents Introduction to VMware Adapter for SAP LVM... 3 Product Description... 3 Executive Summary... 3 Target Audience... 3 Prerequisites...

More information

VMware Quick Start Guide

VMware Quick Start Guide VMware Quick Start Guide Quick Start Guide Version 5.8 March 7, 2011 NOTICE The information contained in this document is believed to be accurate in all respects but is not warranted by Mitel Networks

More information

Basic System Administration ESX Server 3.0.1 and Virtual Center 2.0.1

Basic System Administration ESX Server 3.0.1 and Virtual Center 2.0.1 Basic System Administration ESX Server 3.0.1 and Virtual Center 2.0.1 This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a

More information

ESXi Configuration Guide

ESXi Configuration Guide ESXi 4.1 vcenter Server 4.1 This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a new edition. To check for more recent editions

More information

Virtualization with VMware ESX and VirtualCenter SMB to Enterprise

Virtualization with VMware ESX and VirtualCenter SMB to Enterprise Virtualization with VMware ESX and VirtualCenter SMB to Enterprise Course VM-03 5 Days Instructor-led, Hands-on Course Description This is a 5-day intense introduction to virtualization using VMware s

More information

Solution Brief Availability and Recovery Options: Microsoft Exchange Solutions on VMware

Solution Brief Availability and Recovery Options: Microsoft Exchange Solutions on VMware Introduction By leveraging the inherent benefits of a virtualization based platform, a Microsoft Exchange Server 2007 deployment on VMware Infrastructure 3 offers a variety of availability and recovery

More information

Setup for Microsoft Cluster Service ESX Server 3.0.1 and VirtualCenter 2.0.1

Setup for Microsoft Cluster Service ESX Server 3.0.1 and VirtualCenter 2.0.1 ESX Server 3.0.1 and VirtualCenter 2.0.1 Setup for Microsoft Cluster Service Revision: 20060818 Item: XXX-ENG-QNNN-NNN You can find the most up-to-date technical documentation on our Web site at http://www.vmware.com/support/

More information

VMware vcenter Update Manager Administration Guide

VMware vcenter Update Manager Administration Guide VMware vcenter Update Manager Administration Guide vcenter Update Manager 4.0 This document supports the version of each product listed and supports all subsequent versions until the document is replaced

More information

Quick Start Guide for VMware and Windows 7

Quick Start Guide for VMware and Windows 7 PROPALMS VDI Version 2.1 Quick Start Guide for VMware and Windows 7 Rev. 1.1 Published: JULY-2011 1999-2011 Propalms Ltd. All rights reserved. The information contained in this document represents the

More information

VMware vrealize Automation

VMware vrealize Automation VMware vrealize Automation Reference Architecture Version 6.0 and Higher T E C H N I C A L W H I T E P A P E R Table of Contents Overview... 4 What s New... 4 Initial Deployment Recommendations... 4 General

More information

Introduction to Hyper-V High- Availability with Failover Clustering

Introduction to Hyper-V High- Availability with Failover Clustering Introduction to Hyper-V High- Availability with Failover Clustering Lab Guide This lab is for anyone who wants to learn about Windows Server 2012 R2 Failover Clustering, focusing on configuration for Hyper-V

More information

vcenter Chargeback User s Guide vcenter Chargeback 1.0 EN-000186-00

vcenter Chargeback User s Guide vcenter Chargeback 1.0 EN-000186-00 vcenter Chargeback 1.0 EN-000186-00 You can find the most up-to-date technical documentation on the VMware Web site at: http://www.vmware.com/support/ The VMware Web site also provides the latest product

More information

VMware vsphere Data Protection 6.0

VMware vsphere Data Protection 6.0 VMware vsphere Data Protection 6.0 TECHNICAL OVERVIEW REVISED FEBRUARY 2015 Table of Contents Introduction.... 3 Architectural Overview... 4 Deployment and Configuration.... 5 Backup.... 6 Application

More information

Getting Started with Database Provisioning

Getting Started with Database Provisioning Getting Started with Database Provisioning VMware vfabric Data Director 2.0 This document supports the version of each product listed and supports all subsequent versions until the document is replaced

More information

Virtual Managment Appliance Setup Guide

Virtual Managment Appliance Setup Guide Virtual Managment Appliance Setup Guide 2 Sophos Installing a Virtual Appliance Installing a Virtual Appliance As an alternative to the hardware-based version of the Sophos Web Appliance, you can deploy

More information

Virtual Web Appliance Setup Guide

Virtual Web Appliance Setup Guide Virtual Web Appliance Setup Guide 2 Sophos Installing a Virtual Appliance Installing a Virtual Appliance This guide describes the procedures for installing a Virtual Web Appliance. If you are installing

More information

VMware vsphere: Install, Configure, Manage [V5.0]

VMware vsphere: Install, Configure, Manage [V5.0] VMware vsphere: Install, Configure, Manage [V5.0] Gain hands-on experience using VMware ESXi 5.0 and vcenter Server 5.0. In this hands-on, VMware -authorized course based on ESXi 5.0 and vcenter Server

More information

VMware vcenter Log Insight Getting Started Guide

VMware vcenter Log Insight Getting Started Guide VMware vcenter Log Insight Getting Started Guide vcenter Log Insight 1.5 This document supports the version of each product listed and supports all subsequent versions until the document is replaced by

More information

How to Test Out Backup & Replication 6.5 for Hyper-V

How to Test Out Backup & Replication 6.5 for Hyper-V How to Test Out Backup & Replication 6.5 for Hyper-V Mike Resseler May, 2013 2013 Veeam Software. All rights reserved. All trademarks are the property of their respective owners. No part of this publication

More information

Deploying Windows Streaming Media Servers NLB Cluster and metasan

Deploying Windows Streaming Media Servers NLB Cluster and metasan Deploying Windows Streaming Media Servers NLB Cluster and metasan Introduction...................................................... 2 Objectives.......................................................

More information

vsphere Auto Deploy Update 1 ESXi 5.0 vcenter Server 5.0 EN-000847-01

vsphere Auto Deploy Update 1 ESXi 5.0 vcenter Server 5.0 EN-000847-01 Update 1 ESXi 5.0 vcenter Server 5.0 This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a new edition. To check for more recent

More information

VMware vcenter Operations Manager for Horizon Supplement

VMware vcenter Operations Manager for Horizon Supplement VMware vcenter Operations Manager for Horizon Supplement vcenter Operations Manager for Horizon 1.7 This document supports the version of each product listed and supports all subsequent versions until

More information

Trend Micro Incorporated reserves the right to make changes to this document and to the products described herein without notice.

Trend Micro Incorporated reserves the right to make changes to this document and to the products described herein without notice. Trend Micro Incorporated reserves the right to make changes to this document and to the products described herein without notice. Before installing and using the software, please review the readme files,

More information