Veritas Cluster Server 5.1 SP1 Installation and Upgrade Guide

Veritas™ Cluster ServerInstallation and UpgradeGuide

Windows Server 2003

5.1 Service Pack 1

Veritas Cluster Server Installation and ConfigurationGuide

The software described in this book is furnished under a license agreement andmay be usedonly in accordance with the terms of the agreement.

Product version: 5.1 Service Pack 1

Document version: 5.1.SP1.0

Legal NoticeCopyright © 2009 Symantec Corporation. All rights reserved.

Symantec, the Symantec Logo, Veritas, Veritas Storage Foundation are trademarks orregistered trademarks of Symantec Corporation or its affiliates in the U.S. and othercountries. Other names may be trademarks of their respective owners.

The product described in this document is distributed under licenses restricting its use,copying, distribution, and decompilation/reverse engineering. No part of this documentmay be reproduced in any form by any means without prior written authorization ofSymantec Corporation and its licensors, if any.

THEDOCUMENTATIONISPROVIDED"ASIS"ANDALLEXPRESSORIMPLIEDCONDITIONS,REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OFMERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT,ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TOBELEGALLYINVALID.SYMANTECCORPORATIONSHALLNOTBELIABLEFORINCIDENTALOR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING,PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE INFORMATION CONTAINEDIN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE.

The Licensed Software andDocumentation are deemed to be commercial computer softwareas defined in FAR12.212 and subject to restricted rights as defined in FARSection 52.227-19"Commercial Computer Software - Restricted Rights" and DFARS 227.7202, "Rights inCommercial Computer Software or Commercial Computer Software Documentation", asapplicable, and any successor regulations. Any use, modification, reproduction release,performance, display or disclosure of the Licensed Software andDocumentation by theU.S.Government shall be solely in accordance with the terms of this Agreement.

Symantec Corporation350 Ellis StreetMountain View, CA 94043

http://www.symantec.com

http://www.symantec.com

Technical SupportSymantec Technical Support maintains support centers globally. TechnicalSupport’s primary role is to respond to specific queries about product featuresand functionality. TheTechnical Support group also creates content for our onlineKnowledge Base. The Technical Support group works collaboratively with theother functional areas within Symantec to answer your questions in a timelyfashion. For example, theTechnical Support groupworkswithProductEngineeringand Symantec Security Response to provide alerting services and virus definitionupdates.

Symantec’s maintenance offerings include the following:

■ A range of support options that give you the flexibility to select the rightamount of service for any size organization

■ Telephone and Web-based support that provides rapid response andup-to-the-minute information

■ Upgrade assurance that delivers automatic software upgrade protection

■ Global support that is available 24 hours a day, 7 days a week

■ Advanced features, including Account Management Services

For information about Symantec’sMaintenance Programs, you can visit ourWebsite at the following URL:

www.symantec.com/business/support/index.jsp

Contacting Technical SupportCustomerswith a currentmaintenance agreementmay access Technical Supportinformation at the following URL:

www.symantec.com/business/support/contact_techsupp_static.jsp

Before contacting Technical Support, make sure you have satisfied the systemrequirements that are listed in your product documentation. Also, you should beat the computer onwhich theproblemoccurred, in case it is necessary to replicatethe problem.

When you contact Technical Support, please have the following informationavailable:

■ Product release level

■ Hardware information

■ Available memory, disk space, and NIC information

■ Operating system

http://www.symantec.com/business/support/index.jsp

http://www.symantec.com/business/support/contact_techsupp_static.jsp

■ Version and patch level

■ Network topology

■ Router, gateway, and IP address information

■ Problem description:

■ Error messages and log files

■ Troubleshooting that was performed before contacting Symantec

■ Recent software configuration changes and network changes

Licensing and registrationIf your Symantec product requires registration or a license key, access ournon-technical support Web page at the following URL:

customercare.symantec.com

Customer serviceCustomer Care information is available at the following URL:

www.symantec.com/customercare

Customer Service is available to assist with the following types of issues:

■ Questions regarding product licensing or serialization

■ Product registration updates, such as address or name changes

■ General product information (features, language availability, local dealers)

■ Latest information about product updates and upgrades

■ Information about upgrade assurance and maintenance contracts

■ Information about the Symantec Buying Programs

■ Advice about Symantec's technical support options

■ Nontechnical presales questions

■ Issues that are related to CD-ROMs or manuals

Documentation feedbackYour feedback on product documentation is important to us. Send suggestionsfor improvements and reports on errors or omissions. Include the title anddocument version (located on the second page), and chapter and section titles ofthe text on which you are reporting. Send feedback to:

[email protected]

http://customercare.symantec.com

http://www.symantec.com/customercare

mailto:[email protected]

Maintenance agreement resourcesIf you want to contact Symantec regarding an existing maintenance agreement,please contact the maintenance agreement administration team for your regionas follows:

[email protected] and Japan

[email protected], Middle-East, and Africa

[email protected] America and Latin America

Additional enterprise servicesSymantec offers a comprehensive set of services that allow you tomaximize yourinvestment in Symantec products and to develop your knowledge, expertise, andglobal insight, which enable you to manage your business risks proactively.

Enterprise services that are available include the following:

These solutions provide early warning of cyber attacks, comprehensive threatanalysis, and countermeasures to prevent attacks before they occur.

SymantecEarlyWarningSolutions

These services remove the burdenofmanaging andmonitoring security devicesand events, ensuring rapid response to real threats.

Managed Security Services

Symantec Consulting Services provide on-site technical expertise fromSymantec and its trustedpartners. SymantecConsultingServices offer a varietyof prepackaged and customizable options that include assessment, design,implementation,monitoring, andmanagement capabilities. Each is focused onestablishing andmaintaining the integrity and availability of your IT resources.

Consulting Services

Educational Services provide a full array of technical training, securityeducation, security certification, and awareness communication programs.

Educational Services

To access more information about Enterprise services, please visit our Web siteat the following URL:

www.symantec.com

Select your country or language from the site index.




www.symantec.com

Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Chapter 1 Pre-installation and planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Installation requirements ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Hardware requirements ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Network requirements ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Supported browsers ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Supported operating systems and application versions .... . . . . . . . . . . . . . 12Licensing .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Installation planning .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19About Symantec Product Authentication Service ... . . . . . . . . . . . . . . . . . . . . . . 19About Veritas Cluster Server Management Console ... . . . . . . . . . . . . . . . . . . . 20About notification .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21About global clusters ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Best practices ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Recovery tools ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Chapter 2 Installing and Configuring Veritas ClusterServer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

About installing VCS .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Installing VCS using the product installer ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Before installing VCS .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Installing VCS .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24After installing VCS .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Installing VCS using the command line .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Repairing the installation .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Updating VCS components ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Adding or removing features ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Changing the default password after installing VCS client ... . . . . . . . . . . . . . . . . 33Configuring VCS .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Chapter 3 Uninstalling Veritas Cluster Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Uninstalling using the product installer ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Uninstalling from the command line .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Contents

Uninstall command examples ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Chapter 4 Upgrading Veritas Cluster Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Upgrading the VCS cluster to VCS 5.1 SP1 .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Before you upgrade to 5.1 SP1 .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Starting to upgrade the cluster to 5.1 SP1 .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45After you upgrade the cluster to 5.1 SP1 .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Upgrading an Exchange server cluster ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Upgrade scenarios ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Upgrade tasks ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Upgrading a SQL server cluster ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Upgrade scenarios ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Upgrade tasks ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Upgrading from Microsoft SQL Server 2000 to SQL Server

2005 .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Upgrading fromMicrosoft SQLServer 2000or2005 toSQLServer

2008 .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54Upgrading the Microsoft service packs ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Upgrading to Microsoft Exchange 2003 SP2 in a VCSenvironment .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Upgrading to Microsoft Exchange 2007 SP1 or SP2 in a VCSenvironment .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Upgrading Microsoft SQL 2000 to SP4 in a VCSenvironment .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Upgrading Microsoft SQL 2005 to SP1 in a VCSenvironment .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Upgrading Microsoft SQL 2005 to 2005 SP2 or later in a VCSenvironment .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Upgrading Microsoft SQL 2008 to 2008 SP1 in a VCSenvironment .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Appendix A Services and ports used by VCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

About VCS services and ports ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Contents8

Pre-installation andplanning

This chapter includes the following topics:

■ Installation requirements

■ Installation planning

■ Best practices

■ Recovery tools

Installation requirementsVeritas Cluster Server is supported on Windows-certified network serverscontaining one or more processors. Veritas Cluster Server supports clusters ofup to 32 nodes.

The following sections provides details on the other installation requirements.

Hardware requirementsTo determine the approved hardware refer to, the Hardware Compatibility Liston the Symantec Support Web site.


Table 1-1 provides the details on some of basic hardware requirements.

Table 1-1 Hardware requirements

■ Minimum required: 1GB

■ Recommended: 2GB

Memory

1Chapter


Table 1-1 Hardware requirements (continued)

1 GBDisk space

■ Minimum required: 300 MHz Pentium II

■ Recommended: 550 MHz Pentium III or higher

System processor

■ Recommended: 1024 x 768 pixels or higher

VCS Cluster Manager ( Java Console and ClusterManagement Console) requires an 8-bit (256 color)display and a graphics card able to render 2D images.

Display resolution

■ Shared disks to support applications that migratebetween nodes in the cluster. Campus clustersrequiremore than one array formirroring. Disasterrecovery configurations require one array for eachsite.

■ SCSI or Fibre Channel Host Bus Adapters (HBAs),or iSCSI Initiator supported NICs to access sharedstorage.

■ Two NICs: one shared public and private, and oneexclusively for the private network; Symantecrecommends three NICs: one public and two for theVCS private network.

System requirememts

Network requirementsEnsure that youhaveperformed the following tasks andkept the requirednetworkinformation handy, before you install Veritas Cluster Server.

■ Verify that the systemsonwhich you install the software are part of aWindowsActive Directory domain.

■ Ensure that the static IP addresses are available for the following purposes:

■ One IP address per site for each virtual server.

■ One IP address for each physical node in the cluster

■ One IP address per cluster when configuring Notification and VCS WebConsole. The same IP address can be used for other options, such as GCO.

■ Configure name resolution for each node.

■ Verify that the DNS Services are available. AD-integrated DNS or BIND 8.2 orhigher are supported. Make sure a reverse lookup zone exists in the DNS.Refer to the application documentation for instructions on creating a reverselookup zone.

Pre-installation and planningInstallation requirements

10

■ DNS scavenging affects virtual servers configured inVCS, because the Lanmanagent uses Dynamic DNS (DDNS) to map virtual names with IP addresses. Ifyou use scavenging, then you must set the DNSRefreshInterval attribute forthe Lanman agent. This will enable the Lanman agent to refresh the resourcerecords on the DNS servers.Refer to the Lanman agent description in the Veritas Cluster Server BundledAgents Reference Guide for more information.

■ Make sure that the NetApp filers and the systems on which you plan to installVCS reside in the same domain.

■ Make sure that the NetApp filers are reachable; ensure that you can ping thefilers using the DNS name.

■ If you plan to set up a disaster recovery configuration, make sure that:

■ The volumes at both sites are of the same size.

■ The NetApp filers can replicate in both directions.

■ Configure the Common Internet File System (CIFS) for each volume.Refer to the Network Appliance documentation for instructions.

■ If you plan to use Fibre Channel (FC) for connecting the LUNs, type hba_infoon the command prompt, and verify that the FC initiators are displayed.If FC initiators are not displayed, install themini port driver provided by yourvendor and run the command again to verify that the FC initiators aredisplayed.

■ Ensure that the LUNs aremounted. In case ofMulti Pathing I/O (MPIO), ensurethat the LUNs are mounted using the required initiators.

Note:MPIO support is available only with FC.

■ Donot install VCS on servers that are assigned the role of aDomain Controller.Configuring a cluster on a domain controller is not supported.

■ If the domain controller and the computer running the installation programare on different subnets, the installer may be unable to locate the computersselected for installation. In this situation, after the installation programdisplays an error message, type the host names and the IP addresses of themissing computers manually.

Supported browsersVeritas Cluster Server Management Console is supported on the followingbrowsers:

11Pre-installation and planningInstallation requirements

■ Microsoft Internet Explorer 6.0 with SP2 or newer

■ Firefox 1.5 or newer

Veritas ClusterManagement Console requires theMacromedia Flash Plugin v8.0.

Supported operating systems and application versionsThis section provides details on the supported application versions and theoperating systems.

You must install the operating system in the same path on all systems. Forexample, if you install Windows 2003 on C:\WINDOWS of one node, installationson all other nodesmust be on C:\WINDOWS.Make sure that the same drive letteris available on all nodes and that the system drive has adequate space for theinstallation.

Note: All VCS nodes must run the same Windows operating system and servicepack level as well as the same VCS version and service pack level.

Supported operating systemsVCS supports the following Windows operating systems.

For the latest information on supported software, also see the SoftwareCompatibility list at:

http://entsupport.symantec.com/docs/302145

Your server must run one of the following operating systems to install the VCSserver components:

■ Windows Server 2003 (32-bit): Standard Edition, Enterprise Edition, orDatacenter Edition (SP2 required for all editions)

■ Windows Server 2003 R2 (32-bit): Standard Edition, Enterprise Edition, orDatacenter Edition (SP2 required for all editions)

■ Windows Server 2003 (32-bit): Web Edition: fully supports SFW and supportsonly file share for SFW HA (SP2 required for all editions)

■ Windows Server 2003 for 64-bit Itanium (IA64): Enterprise Edition orDatacenter Edition (SP2 required for all editions)

■ Windows Server 2003 x64 Editions (for AMD64 or Intel EM64T): Standard x64Edition, Enterprise x64 Edition, or Datacenter x64 Edition (SP2 required forall editions)


12


■ Windows Server 2003 x64 R2 Editions (for AMD64 or Intel EM64T): Standardx64 R2 Edition, Enterprise x64 R2 Edition, or Datacenter x64 R2 Edition (SP2required for all editions)

Your system must run one of the following operating systems to install the VCSor VCS client software:

■ Any one of the operating system versions, editions, and architectures that theServer Components are supported on.

■ Windows XP x86, x64 (SP3 required)

■ Windows Vista x86, x64: Ultimate Edition, Business Edition, PremiumEdition(SP1 or SP2 required)

Microsoft Exchange servers and their operating systemsTable 1-2 lists the supported Microsoft Exchange servers and the correspondingoperating systems

Table 1-2 Mircosoft Exchange servers and operating systems

Operating systemsMicrosoft Exchange servers

■ Windows Server 2003 x64 (StandardEdition, Enterprise Edition, DatacenterEdition) including SP1 andSP2 for all theeditions.

■ Windows Server 2003 R2 x64 (StandardEdition, Enterprise Edition, DatacenterEdition) including SP1 and SP2 for alleditions.

Microsoft Exchange Server 2007 StandardEdition or Enterprise Edition on WindowsServer 2003 (including SP1 and SP2)

■ Windows Server 2003 (32-bit) (StandardEdition, EnterpriseEdition, orDatacenterEdition) including SP1 and SP2 for alleditions.

■ Windows Server 2003 R2 (32-bit)(Standard Edition, Enterprise Edition, orDatacenter Edition) including SP1 andSP2 for all editions.

Microsoft Exchange Server 2003 StandardEdition or Enterprise Edition on WindowsServer 2003 (including SP1 and SP2)

Microsoft SQL servers and their operating systemsTable 1-3 lists the supported Microsoft SQL servers and the correspondingoperating systems


Table 1-3 Microsoft SQL Servers and operating systems

Operating systemsMicrosoft SQL Servers

Windows Server 2003 (32-bit) StandardEdition, Enterprise Edition, or DatacenterEdition (SP1 required for all editions, SP2supported)

Windows Server 2003 R2 (32-bit) StandardEdition, Enterprise Edition, or DatacenterEdition

Microsoft SQLServer 2000StandardEditionor Enterprise Edition (SP4 required)

Windows Server 2003 for Itanium-basedsystems: Enterprise Edition or DatacenterEdition (SP1 required for all editions, SP2supported)

Microsoft SQL Server 2000 (64- bit)Enterprise Edition

WindowsServer2003x64Editions: Standardx64 Edition, Enterprise x64 Edition, orDatacenter x64 Edition (SP1 required for alleditions, SP2 supported)

Windows Server 2003 x64 R2 Editions:Standard x64 R2 Edition, Enterprise x64 R2Edition, or Datacenter x64 R2 Edition (SP1required for all editions, SP2 supported)

Microsoft SQLServer 2000StandardEditionor Enterprise Edition (SP4 required for alleditions)

■ WindowsServer 2003 (32-bit) EnterpriseEdition or Datacenter Edition (SP1required for all editions, SP2 supported)

■ Windows Server 2003 R2 (32-bit)Standard Edition, Enterprise Edition, orDatacenter Edition (SP2 supported for alleditions)

■ Windows Server 2003 Standard x64Edition, Enterprise x64 Edition, orDatacenter x64 Edition (SP2 supportedfor all editions)

■ Windows Server 2003 x64 R2 Editions:Standard x64 R2 Edition, Enterprise x64R2 Edition, or Datacenter x64 R2 Edition(SP2 supported for all editions)

Microsoft SQL Server 2005, (32- bit)Standard Edition or Enterprise Edition (SP1,SP2 and SP3 for all editions)


14

Table 1-3 Microsoft SQL Servers and operating systems (continued)

Operating systemsMicrosoft SQL Servers

■ Windows Server 2003 for Itanium-basedsystems:EnterpriseEditionorDatacenterEdition (SP1 required for all editions, SP2supported)

■ Windows Server 2003 Standard x64Edition, Enterprise x64 Edition, orDatacenter x64 Edition (SP2 supportedfor all editions)

■ Windows Server 2003 x64 R2 Editions:Standard x64 R2 Edition, Enterprise x64R2 Edition, or Datacenter x64 R2 Edition(SP2 supported for all editions)

Microsoft SQL Server 2005, (64- bit)Standard Edition or Enterprise Edition (SP1,SP2 and SP3 for all editions)

■ Windows Server 2003 (32-bit) StandardEdition, Enterprise Edition orDatacenterEdition (SP2 required)

■ Windows Server 2003 R2 (32-bit)Standard Edition, Enterprise Edition, orDatacenter Edition (SP2 required)

■ Windows Server 2003 for Itanium-basedSystemsEnterpriseEditionorDatacenterEdition (SP2 required for both)

■ Windows Server 2003 Standard x64Edition, Enterprise x64 Edition, orDatacenter x64 Edition (SP2 required)

■ Windows Server 2003 x64 Editions (forAMD64 or Intel EM64T): Standard x64R2 Edition, Enterprise x64 R2 Edition, orDatacenter x64R2Edition (SP2 required)

Microsoft SQL Server 2008, 32-bit StandardEdition or Enterprise Edition orWebEdition(including SP1)


■ Windows Server 2003 Standard x64Edition, Enterprise x64 Edition, orDatacenter x64 Edition (SP2 required)

■ Windows Server 2003 x64 Editions (forAMD64 or Intel EM64T): Standard x64R2 Edition, Enterprise x64 R2 Edition, orDatacenter x64R2Edition (SP2 required)

Microsoft SQL Server 2008 (64-bit StandardEdition or Enterprise Edition or EnterpriseIA64 Edition orWeb Edition (including SP1)


Note:Microsoft SQL Server 2000 and Microsoft SQL Server 2005 can exist in thesame cluster and operate on or fail over to the same systems. However, only onedefault instance can exist on a system at one time. Additional instances thatoperate on or fail over to that system must be named instances. The number ofnamed instances is limited only by the normal limit of instances for that versionof SQL Server.

Note: Similarly, Microsoft SQL Server 2005 and Microsoft SQL Server 2008 canexist in the same cluster and operate on or fail over to the same systems.However,only one default instance can exist on a system at one time. Additional instancesthat operate on or fail over to that system must be named instances. The numberof named instances is limited only by the normal limit of instances for that versionof SQL Server.

Oracle versions and their operating systemsTable 1-4 lists the supported Oracle versions and the corresponding operatingsystems

Table 1-4 Oracle versions and operating systems

Operating systemsOracle versions

■ Windows Server 2003 (32-bit) StandardEdition, EnterpriseEdition, orDatacenterEdition (SP2 required for all editions)

■ Windows Server 2003 (32-bit) R2Standard Edition, Enterprise Edition, orDatacenter Edition (SP2 required for alleditions)


Oracle 9i, Release 2 (9.2.0.2) StandardEdition, Enterprise Edition

Oracle 10g, Release 1 (10.1.0.2) StandardEdition, Enterprise Edition


16

Table 1-4 Oracle versions and operating systems (continued)

Operating systemsOracle versions






Oracle 10g, Release 2 (10.2.0.1.0) StandardEdition, Enterprise Edition

Supported Network Appliance applicationsThe supported versions of Network Appliance applications are as follows:

■ NetworkAppliance SnapManager for Exchange 3.2withExchangeServer 2003

■ NetworkAppliance SnapManager for Exchange 4.0withExchangeServer 2007

■ Network Appliance SnapManager for SQL 2.0

■ Network Appliance Data ONTAP 7.3

■ Data ONTAP DSM for Windows MPIO 3.1, 3.2

■ FCP Host Utilities for Native OS 3.0, 4.0, 5.0

■ Microsoft iSCSI software initiator version 2.03 or later versions

■ Network Appliance SnapDrive 4.1, 4.2.1, 5.0 and 6.0When installing SnapDrive, youmust specify a user account in the SnapDriveService Credentials dialog box. The user account must be a domain user andpart of the Administrators group of the local system and the filer.

■ Microsoft iSCSI software Initiator 2.02 and 2.05

■ NetApp FCP Attach Kit 3.0, Windows Host Utilities 3.0If you plan to use Fibre Channel (FC) for connecting the LUNs, ensure that youinstall the NetApp FCP Attach Kit, Windows Host Utilities, or the hotfixes


prompted for, on all the cluster nodes. Refer to NetApp documentation formore details.

LicensingEach copy of Veritas Cluster Server including all options and agents, whetherused on a physical server or within a virtual machine, must be licensed accordingto the conditions set forth in the sections below. Each Licensed Software licensespecifies the number of instances of the licensed software you may run on aparticular server at one time.

Table 1-5 lists Veritas Cluster Server editions and the additional licensing termsthat apply.

Table 1-5 Veritas Cluster Server licensing terms

Veritas Cluster Server licensing termsMicrosoft Operating System Edition

A separate license for the licensed softwareis required for each virtual or physicalserver, where the software is installed.

■ Server Edition

■ Standard Edition

■ Web Edition

For each license, you may run one instanceof the licensed software on one physicalserver andup to four simultaneous instancesof the licensed software on virtual serverslocated on the physical server.

■ Advanced Edition

■ Enterprise Edition

For each license, you may run one instanceof the licensed software on one physicalserver and an unlimited number of virtualservers located on the physical server.

Datacenter Edition

Evaluation license keyAn evaluation license key is embedded in the product. To use this key, click Nextat the license key entry screen of the product installer. This license key is onlyvalid for a limited evaluation period.

Virtual Server license policyEach copy of the Veritas Cluster Server including all options and agents, whetherused on a physical server orwithin a virtualmachinemust be separately licensed.Each Licensed Software license specifies the number of instances of the LicensedSoftware you may run on a particular server at one time.


18

License managementThe product installer allows you to add and remove specific licenses. Adding alicense for an option does not install the option. Use the Add/Remove functionto install an option. License keys support installation on multiple systems.

Note:License keys for releases earlier than4.3 ofVCS are not supported in release5.1 of VCS. A default evaluation license key is supplied for your use. This licensekey is valid for a limited evaluation period only. You must purchase the productto obtain a permanent license key.

Installation planningYou can install VCS using the product installer or the CLI. During the installationyou can also opt to install the other applicable options. You may also choose toinstall the product simultaneously on more than one system.

After the installation is complete, run the VCS ConfigurationWizard to completethe VCS cluster configuration. The VCS Configuration Wizard presents theopportunity to configure optional VCS features including security options, ClusterManagement Console, notification, and the global cluster wide-area connectionresource.

Depending on your environment you may choose to configure the SymantecProduct Authentication Service and the ClusterManagement Console on systemsoutside the cluster.

Review the following sections and decide how you want to configure yourenvironment:

■ About Symantec Product Authentication Service

■ SFW HA upgrade and Veritas Netbackup

■ About Veritas Cluster Server Management Console

■ About notification

■ About global clusters

About Symantec Product Authentication ServiceSymantec Product Authentication Service allows the security administrator toconfigure authentication to provide a single sign-on service for Symantecapplications. In this case, users need log-on only once to a single Symantecapplication, and other applications can thenuse the credentials acquired throughthe first logon.

19Pre-installation and planningInstallation planning

Symantec Product Authentication Service provides the ability to configure acluster in secure mode. Symantec Product Authentication Service securescommunication between cluster nodes and clients, including the Java console, byusing digital certificates for authentication and SSL to encrypt communicationover the public network.

To configure the cluster in securemode, VCS requires you to specify and configurea system in your environment as a root broker and all nodes in the cluster asauthentication brokers.

Table 1-6 defines the root broker and authentication broker.

Table 1-6 Root and authentication broker definitions

DescriptionBroker type

A root broker serves as the main registration and certificationauthority.

It is the single authoritywhich validates requests fromauthenticationbrokers that are installed on the (cluster) systems.

Root broker

Authentication brokers serve as intermediate registration andcertification authorities. Authentication brokers have certificates thatare signed by the root. Each node in the cluster serves as anauthentication broker.

Authenticationbroker

For best practices andoptions for configuring the root broker in your environment,refer to the Veritas Storage Foundation™ and High Availability Solutions QuickStart Guide for Symantec Product Authentication Service.

About Veritas Cluster Server Management ConsoleVeritas Cluster Server Management Console is a high availability managementsolution that enables monitoring and administering clusters from a single webconsole.

You can configure Cluster Management Console to manage a single cluster,multiple clusters, or both:

■ If youwant touse theClusterManagementConsole tomanagemultiple clusters,you must set up a standalone management server.

■ If youwant to use the ClusterManagement Console tomanage a single cluster,choose the option to configure the Cluster Management Console, also knownas theWebconsole fromtheVCSConfigurationWizard. Configuring theClusterManagement Console may be done during initial cluster configuration or at alater time.

Pre-installation and planningInstallation planning

20

For additional information about theVeritas Cluster ServerManagement Console,refer to the Veritas™ Cluster Server Management Console Implementation Guide.

Contact customer service at the followingURL to request the latest version of theguide:

www.symantec.com/techsupp/

About notificationYou can configure VCS to send event notification either through SMTP emailnotification or SNMP traps.

Configuring the notifier process may be done during initial cluster configurationor at a later time using the VCS Configuration Wizard.

For additional information about the VCS Configuration Wizard, refer to theVeritas Cluster Server Administrator’s Guide.

About global clustersA global cluster consists of two or more clusters linked together. Global clustersprovide the ability to fail over applications between geographically distributedclusters when disaster occurs.

Global clusters may be configured using the Global Group Configuration Wizard.This requires a wide-area connector resource for inter cluster communication.This resource can be optionally configured using the VCS Configuration Wizard.

For informaton about the Global Group Configuration Wizard and VCSConfiguration Wizard, refer to Veritas Cluster Server Administrator’s Guide.

Best practicesSymantec recommends that you perform the following tasks before you begin toinstall VCS:

■ Verify that you have three network adapters (two NICs exclusively for theprivate network and one for the public network). When using only two NICs,lower the priority of oneNIC anduse the low-priorityNIC for public andprivatecommunication.

■ Route eachprivateNIC through a separate hub or switch to avoid single pointsof failure.

■ NIC teaming is not supported for the private network.

21Pre-installation and planningBest practices

www.symantec.com/techsupp/

■ Verify that you have set the Dynamic Update option for the DNS server toSecure Only.

■ Configure Microsoft Exchange Server and Microsoft SQL Server on separatefailover nodes within a cluster.

Recovery toolsSymantec provides a cleanup script and 'vxexplorer' recovery tool for the failedVCS 5.1 SP1 installs, uninstalls or upgrades. This script and recovery tool can bedownloaded from the following Symantec link:


Pre-installation and planningRecovery tools

22


Installing and ConfiguringVeritas Cluster Server


■ About installing VCS

■ Installing VCS using the product installer

■ Installing VCS using the command line

■ Repairing the installation

■ Updating VCS components

■ Adding or removing features

■ Changing the default password after installing VCS client

■ Configuring VCS

About installing VCSThis chapter describes the process for installing Veritas Cluster Server 5.1 SP1.

You can install VCS using either the product installer or the command lineinterface (CLI).

Installing VCS using the product installerThis section outlines the tasks for installing VCS, using the product installer.

2Chapter

Note: Before installing Veritas Cluster Server, make sure you have uninstalledany previous versions of SFW or SFW HA.

For installing VCS 5.1 SP1 over any previous version of VCS, refer to See“Upgrading the VCS cluster to VCS 5.1 SP1” on page 41.

Before installing VCSBefore installing the software on remote systems running Windows 2003, youmustmodify thedriver signingoptions to ignorewarningmessages about softwareauthentication.

To modify the driver signing options

1 Open the Driver Signing Options dialog box by using either of the followingmethods:

■ FromWindows Explorer, right-click MyComputer, and click Properties.On the Hardware tab, click Driver Signing.

■ Open the Control Panel and double-click System. On the Hardware tab,click Driver Signing .

2 In the Driver Signing Options dialog box, select Ignore, and click OK.

Installing VCSTo install the product using the installer

1 FromWindows Explorer, navigate to the root directory of the Veritas ClusterServer installation media and double-click Setup.exe.

2 Click Product Installation in the left pane, then click the product name,Veritas Cluster Server 5.1 SP1 for Windows.

3 Click Complete/Custom.

The Complete/Custom installation installs server components and optionalclient components. Click Administrative Console if you wish to install onlythe client components. This will install the VCS Java Console.

4 Review the information on the Welcome panel and click Next.

5 Read the License Agreement by using the scroll arrows in the view window.If you agree to the license terms, click I agree to the terms of the licenseagreement and then click Next.

Installing and Configuring Veritas Cluster ServerInstalling VCS using the product installer

24

6 In the Enter a license key field, type the license key, click Add, and then clickNext. The License Key Details section displays more information about theselected key.

If you do not have a license key, click Next to use the embedded evaluationlicense key.

To delete a license key, select the key from the key list and click Remove.

7 On the Option Selection panel, check the following product options and clickNext:

■ Veritas Cluster Server 5.1 SP1 for Windows (Server Components)

■ Global Clustering Option - if you plan to configure a disaster recoveryenvironment.

■ High Availability Hardware Replication Agents

■ High Availability Application Agents

■ High Availability Database Agents

■ Veritas Cluster Server Database Agent for SQL

■ Veritas Cluster Server Database Agent for Oracle

■ Enterprise Vault (EV) Cluster Setup Wizard

■ Product Documentation

■ Veritas Cluster Server 5.1 SP1 for Windows (Client Components) - Thisinstalls the VCS Java Console on the same nodes where the servercomponents are installed.

8 On the Computer Selection panel, specify the domain and nodes for theinstallation and click Next.

Select the domain from the drop-downlist.

Domain

Select the computer name from thedropdown list. This may take some timeto populate depending on the domain andnetwork size, speed, and activity.Alternatively, if you know the computername, type the name in the Computerfield.

Computer

Click Add to add the computer forinstallation.

Add

25Installing and Configuring Veritas Cluster ServerInstalling VCS using the product installer

The Selected computers for installationsection displays the list of computers thatyouhaveadded for installation.To removea computer, click a computer name andclick Remove.

Selected computers for installation

The Install Path field displays the defaultpath for installation. To specify a differentinstallation path for a computer:

■ Select the computer name from theSelected computers for installationlist.

■ Type the path in the Install Path field.

■ Click Change and then click Yes toconfirm the changes. To restore thedefault installation path for acomputer: Select the computer namefrom the Selected computers forinstallation list and then clickDefault.

Install Path

9 After the installer validates the systems for the installation, click Next. If anerror occurs, address the problemdescribed in theDetails box, clickValidateAgain, and click Next.

10 Review the summary information and click Install. If necessary, click Backto make changes.

11 If an installation is not successful on any of the systems, the status screenshows a failed installation. If the installation is successful on all systems,click Next after the progress indicator shows the installation is completed.If a security alert asks you to accept the Veritas driver software, click Yes.

12 Review the installation report and click Next.

13 Click Finish to complete the installation.

14 Click Yes to reboot the local node.

After installing VCSToensurea secure systemenvironment, after completing the installation sequence,reset the driver signing options on each computer to the original state of Warnor Block.

Installing and Configuring Veritas Cluster ServerInstalling VCS using the product installer

26

To reset the driver signing options

1 Open the Control Panel and click System.

2 Select the Hardware tab and click Driver Signing.

3 In the Driver Signing Options dialog box, reset the option to Warn or Block.

4 Click OK to close the Driver Signing Options dialog box, and then click OKagain to close the System window.

5 Repeat for each computer.

Installing VCS using the command lineYou can perform a silent installation from the command prompt using theSetup.exe command. A silent installation can be performed only on one node ata time. See the examples at the end of this section for reference.

To start the installation from the command window

1 Insert the product software disc into a drive connected to the system.

2 Click Start > Run.

3 Enter cmd in the Open field and click OK.

4 From the command window, navigate to the root directory of the productsoftware disc.

5 Use the following command to install the software:

Setup.exe /s Solution=<Solution> Install_mode=<InstallMode>

Installdir=<"InstallDirPath"> Reboot=<RebootMode>

target=<”machine name”> Licensekey=<"LicenseKey">

options=<"a,b,c,...">

where the maximum length of the argument string is 512 characters.

Note:To install the server andmatching client components, run the Setup.exe/s command twice, once with the Solution parameter set for the servercomponent and the next set for the client component. If you use a script toinstall the server and client, consider first installing the client and then theserver, so that the script can reboot the system after server installation.

Parameters for setup.exe

Table 2-1 lists the information about the possible parameter values for thesetup.exe.

27Installing and Configuring Veritas Cluster ServerInstalling VCS using the command line

Table 2-1 Possible parameter values

Set for silent mode./s

Set to indicate an install or uninstall.

1 = To install

4 = To repair

5 = To uninstall

The default setting is 1.

Example: Install_mode=1

Install_mode

Set to the type of installation.

6 = VCS Server Components

7 = VCS Client Components

The default setting is 6.

Example: Solution=6

Solution

Set the installation directory path. The pathmust start and end with a quotation mark.

Thedefault setting isSystemDrive: \Programfiles\Veritas

Example:

INSTALLDIR="C:\InstallationDirectory"

Note: This is an optional parameter.

Install_dir

Setting for the automatic reboot of thesystemat the completion of the installation.

0 = No reboot

1 = Reboot

The default setting is 0 for no system reboot.

Example: Reboot=1

Reboot

Set the node name. Specify only one node ata time.

The local node is the default setting whenthe node is unspecified.

Example: Node=”PC177VM-3”

Node

Installing and Configuring Veritas Cluster ServerInstalling VCS using the command line

28

Table 2-1 Possible parameter values (continued)

Specify the machine name for the systemwhere youwant to install the software.Makesure you place the machine name betweenquotes.

Local node is the default setting

Example: “PC177VM-3”

This is an optional parameter.

Target

Set the license key for the installation. Entermultiple keys by separating them with acomma (e.g. 123-345-567-789- 123,321-543-765-789-321, etc.) The license keymust start and end with a quotation mark(").

LicenseKey has no default setting.

Example:LICENSEKEY="123-234-123-234-345"

LicenseKey

Set the desired options, if any. The optionmust start and end with a quotation mark("). Multiple options can be entered, use acomma as a separator.

There are no default settings.

The options for VCS are:

■ ntap

■ GCO

■ exchange

■ sql

Example: OPTIONS="GCO"

Options

Setup.exe example: Client installation

This sample command installs the client components at the specified installationpath and tells the system not to reboot at the end of the installation.

Setup.exe /s Solution=7 Install_mode=1

Installdir="C:\InstallationDirectory"

Setup.exe example: Server installation

This sample command installs the server components in thedirectoryC:\InstallationDirectory and tells the system to reboot at the end of

29Installing and Configuring Veritas Cluster ServerInstalling VCS using the command line

the installation. It also installs with a license key of 123-234-123-234-345, andwith the GCO option.

Setup.exe /s Solution=6 Install_mode=1

INSTALLDIR="C:\InstallationDirectory" REBOOT=1

licensekey="123-234-123-234-345" options="GCO,SQL"

Repairing the installationThe product installer can repair an existing installation of the VCS client andserver components.

The Repair option restores the installation to its original state. This option fixesmissing or corrupt files, shortcuts, and registry entries on the local computer.

When repairing an VCS installation, you must first stop the VERITAS HighAvailability Engine. To stop the VERITAS High Availability Engine, type thefollowing on the command prompt:

C:\>hastop -local

Note:Before running the above command, you should also take steps to save yourconfiguration to another system for safe keeping, and failover the service groupsfor your applications to another node.

Note: You can only repair the installation on the local system.

To repair the installation

1 Open the Windows Control Panel and click Add or Remove Programs.

2 Select Change or Remove Programs.

3 Select the option for the Veritas Storage Foundation (Server Components).

4 The Symantec Product Installer screen appears. Select Repair. Click Next.

5 On theValidation screen, the installer checks theprerequisites for the systemsand displays the results. Review the information and click Next.

If a system fails validation, click the system in the systems list to displayinformation about the failure. Address the problem and clickValidateAgainto repeat the validation process.

6 On the Summary screen, review the information and click Repair to beginthe repair process.

Installing and Configuring Veritas Cluster ServerRepairing the installation

30

7 On the Repair Status screen, review the status messages and the progress ofthe repair.

If a repair fails, click Next to review the report and address the reason forfailure. You may have to uninstall and reinstall the software.

8 When complete, review the repair summary and click Next.

9 On the Thank You screen, click Finish.

Updating VCS componentsAfter an installation, you may need to update your components. The productinstaller allows you to update the installed client and server components.

To update VCS components



3 Select the option for Veritas Cluster Server and click Change.

4 The Symantec Product Installer screen appears. Select LiveUpdate. ClickNext.

5 The LiveUpdate screen appears. Choose to check if updates are availableautomatically by selecting On (automatically check for updates) or chooseto check if updates are available manually by selecting Off (manually checkfor updates).

6 Choose a LiveUpdate mode. If On (automatically check for updates) isselected, you have a choice to select Express to have updates automaticallydownloaded and installed, or select Interactive to view a list of availableupdates and choose which to download and install on your computer.

7 Select Check for latest update after "Finish" is clicked. Click Finish.

Adding or removing featuresAfter you have installed VCS, you may need to add or remove features to yourapplication. The product installer allows you to add or remove features.

Note: You can only add or remove features on the local system.

31Installing and Configuring Veritas Cluster ServerUpdating VCS components

To add or remove features



3 Select the option for Veritas Cluster Server and click Change.

4 The Symantec Product Installer screen appears. Select Add or Remove.

Click Next.

5 The Option Selection screen appears. Select or clear the option check boxesin the tree navigation structure to add or remove a component respectively.

Proceed to the following procedure.

To add a license key for an option

1 In the Option Selection screen, right-click on the option and select AddLicense.

2 In the pop-up window that appears, enter the license key for the option andclick OK.

Select the check box to add the option.

3 Click Next.

Proceed to the following procedure.

Validation and Summary

1 On theValidation screen, the installer checks theprerequisites for the selectedoptions and displays the results. Review the information and click Next.


2 On the Summary screen, review the information and click Update to beginthe product update.

3 On theUpdate Status screen, statusmessages are displayed and the progressupdated.

4 When complete, review the summary and click Next.

5 On the Thank You screen, click Finish.

6 In the message box, click Yes to reboot your system.

Installing and Configuring Veritas Cluster ServerAdding or removing features

32

Changing the default password after installing VCSclient

When you install and configure the VCS client components (Java GUI), if you donot choose the secure mode during cluster configuration, the Veritas ClusterServer ConfigurationWizard (VCW) creates a userwith default credentials of username "admin" and password "password".

Make sure that when you configure the cluster using VCW, you create a uniqueuser name and password during the configuration process instead of acceptingthe default values.

Configuring VCSAfter installing the software, set up the components required to runVeritasClusterServer. TheVCSConfigurationWizard sets up the cluster infrastructure, includingLLT and GAB, and provides an option of configuring the Symantec ProductAuthenticationService in the cluster. Thewizardalso configures theClusterServicegroup, which contains resources for ClusterManagement Console (Single ClusterMode) also referred to as Web Console, notification, and global clusters.

■ If you plan to set up a disaster recovery environment, configure the wideareaconnector process for global clusters.

■ When configuring a user account for the VCS Helper service, choose theadministrative account set up on the filer

For instructions, see the chapter onGetting StartedwithVCS in theVeritas ClusterServer Administrator’s Guide.

33Installing and Configuring Veritas Cluster ServerChanging the default password after installing VCS client

Installing and Configuring Veritas Cluster ServerConfiguring VCS

34

Uninstalling Veritas ClusterServer


■ Uninstalling using the product installer

■ Uninstalling from the command line

Uninstalling using the product installerThe Symantec Product Installer enables you to uninstall VCS.

To uninstall the product from remote computers, ensure that the product isinstalled on the local computer.

For uninstalling VCS, you must first unconfigure the cluster. Use the VeritasCluster Wizard (VCW) to unconfigure the cluster. See the Veritas Cluster ServerAdministrator’s Guide for more information.

Note: The changes made to types.cf file after upgrading from VCS 5.1 to VCS 5.1SP1 are lost if you choose to uninstall VCS 5.1 SP1 and roll back to VCS 5.1.

Take a back up of the types.cf file before you uninstall VCS 5.1 SP1 and re-importthe same after the roll back is complete.

To uninstall using the product installer

1 In the Windows Control Panel, select Add or Remove Programs.

2 Click Veritas Cluster Server 5.1 SP1 for Windows (Server Components).

3 Click Remove.

4 Review the information on the Welcome screen and then click Next.

3Chapter

5 On the Options Selection screen, select the checkboxes to uninstall both theclient components and the server components.

Click Next.

6 On the Computer Selection screen, select the systems that you want touninstall from the Domain and Computer drop-down menus and click Add.Optionally, type the computer’s name in the Computer field. Repeat touninstall from other systems.

To remove a system from the Selected computers for uninstallation list,click the system and click Remove.

7 Click Next.

8 On theValidation screen, the installer checks theprerequisites for the selectedsystems and displays the results. Review the information and click Next.


Click Next.

9 The Summary screen appears and displays the settings and systems selectedfor uninstallation.

Click Uninstall.

10 TheUninstall Status screen displays statusmessages and the progress of theinstallation.

If an uninstallation fails, the status screen shows a failed uninstallation. ClickNext to review the report, address the reason for failure, and retry this stepon that computer.

11 When complete, review the Uninstall summary and click Next.

12 Reboot the remote nodes.

Note: You must not reboot the local node now.

13 Select the check box next to the remote nodes that you want to reboot andclick Reboot.

14 When the remote nodes have finished rebooting successfully, the RebootStatus shows Online and the Next button is available. Click Next.

15 Once the remote nodes have rebooted, click Next.

Uninstalling Veritas Cluster ServerUninstalling using the product installer

36

16 On the Thank You screen, click the link to review the log file, review the logfile, and then click Finish.

17 Click Yes to reboot the local system.

Uninstalling from the command lineYou can silently uninstall the VCS software from the command prompt using thesetup.exe command.

The setup.exe command syntax is as follows:

Setup.exe /s INSTALL_MODE=InstallMode

SOLUTIONS="1,2,3,..." [REBOOT=RebootMode] [NODE="SysA"]

Table 3-1displays informationabout thepossible parameter values foruninstallingthe VCS software:

Table 3-1 Parameters for uninstalling the software

UseParameter

Set for silent mode./s

Set to indicate an install or uninstall.

1 = To install

4= To repair

5 = To uninstall

The default setting is 1 to install. Set this parameter to 5 for uninstall.

Example: INSTALL_MODE=5

INSTALL_MODE

Set to the type of uninstallation.

6- VCS 5.1 SP1 (Server Components)

7 - VCS 5.1 SP1 (Client Components)

Example: Solution=6

Note: To uninstall the server and matching client components, runtwo setup.exe /s commands, one with the Solution parameter set forthe server component and the other set for the matching clientcomponent.

SOLUTIONS

37Uninstalling Veritas Cluster ServerUninstalling from the command line

Table 3-1 Parameters for uninstalling the software (continued)

UseParameter

Setting for the automatic reboot of the system at the completion ofthe installation.

0 = No reboot

1 = Reboot

The default setting is 0 for no system reboot.

Example: REBOOT=1

REBOOT

Set the node name.

You can enter only one node at a time.

The local node is the default setting when the node is unspecified.

The machine name of the node must start and end with a quotationmark (").

Example: Node="SysA"

Note: Reboot the system at the end of uninstallation to ensure thatthe VCS drivers for the server component are installed correctly. Youdo not have to reboot after uninstalling the client.

NODE

The followingproceduredescribeshowtouninstall the software fromthecommandprompt.

Note: The changes made to types.cf file after upgrading from VCS 5.1 to VCS 5.1SP1 are lost if you choose to uninstall VCS 5.1 SP1 and roll back to VCS 5.1.

Take a back up of the types.cf file before you uninstall VCS 5.1 SP1 and re-importthe same after the roll back is complete.

To uninstall from the command prompt

1 Open a command window by clicking Start > Run.

2 Enter cmd in the Open field and click OK.

3 In the command window, navigate to the root directory of the product DVD.

4 Use the following command syntax to silently uninstall VCS:

Setup.exe /s INSTALL_MODE=InstallMode

SOLUTIONS="1,2,3,..."

[REBOOT=RebootMode] [NODE="SysA"]

Uninstalling Veritas Cluster ServerUninstalling from the command line

38

Uninstall command examplesThe following uninstall command example completely uninstalls the VCS clientcomponents, and reboots the system at the end of the uninstall process:

Setup.exe /s Solution=7 Install_mode=5 Reboot=0

The following uninstall command example completely uninstalls the VCS servercomponents, and reboots the system at the end of the uninstall process:

Setup.exe /s Solution=6 Install_mode=5 Reboot=1

39Uninstalling Veritas Cluster ServerUninstalling from the command line

Uninstalling Veritas Cluster ServerUninstalling from the command line

40

Upgrading Veritas ClusterServer


■ Upgrading the VCS cluster to VCS 5.1 SP1

■ Upgrading an Exchange server cluster

■ Upgrading a SQL server cluster

■ Upgrading the Microsoft service packs

Upgrading the VCS cluster to VCS 5.1 SP1This sectiondescribes the tasks to be carried outwhenupgrading toVeritas ClusterServer 5.1 SP1.

Note that if you are upgrading from VCS 5.1 or 5.1 AP1, you can choose to rollback to this version by uninstalling SP1. However, if you are upgrading from anyother VCS version, you cannot roll back to the version from which you chose toupgrade the product to 5.1 SP1.

Note: Before upgrading to VCS 5.1 SP1, verify the version of Snapdrive installed.If youhave Snapdrive 3.2 installed and youupgrade toVCS5.1 SP1, all thewizardsthat were working before the upgrade, will stop working. You must upgrade toVCS 5.1 SP1 first and then upgrade the Snapdrive installation to version 4.1 orabove.

4Chapter

Before you upgrade to 5.1 SP1Ensure that you perform the pre-upgrade tasks as mentioned in the followingsections, before you proceed with the actual upgrade steps.

General preparationsWhen upgrading the product, perform the following general pre-upgrade tasks:

■ Back up all your data.

■ Back up the system state.

■ Check the hardware requirements for the software upgrade.

■ Check to see if you need to update the Microsoft Active Directory to supportthe upgrade software.

■ Test the systemafter eachupgrade, especially after applying product upgradesto meet the minimum version required. An incremental upgrade eases thetroubleshooting process.

Removing VCS Management Console 5.1If one or more nodes in the cluster have Veritas Cluster Server ManagementConsole 5.1 installed, youmust remove themanagement console before upgradingVCS. You can reinstall the management console after the upgrade

See “Reinstalling VCS Management Console 5.1” on page 47.

To remove VCS Management Console 5.1

1 Stop the VCS Management Console. If the management console is clustered,take the CMC_MS service group offline.

2 Back up the console’s data directory and datadir.conf files. Typically, the filesare located at one of the following paths:

■ C:\Program Files\Symantec\VRTScmcm

■ C:\Program Files (x86)\Symantec\VRTScmcm

3 Remove VCSManagement Console 5.1 from all nodes in the cluster using theWindows Add/Remove Programs.

Saving and closing the cluster configurationBefore starting the upgrade process, use the VCS Java Console to "save and close"the VCS configuration. This operation involves saving the latest configuration todisk and changing the configuration state to read-only mode. You must also stopVCS before attempting the upgrade process.

Upgrading Veritas Cluster ServerUpgrading the VCS cluster to VCS 5.1 SP1

42

To save and close the cluster configuration

◆ Perform one of the following tasks:

■ From the VCS Java Console, click Save and Close Configuration on theCluster Explorer toolbar.

■ From the command prompt, type the following command.C:\>haconf -dump -makero

Taking the service groups offlineTake all service groups offline before the upgrade.

To take the service groups offline

1 From the command prompt, type:

C:\>hagrp -offline group_name -sys system_name

where group_name is the name of the service group and system_name is thenode on which the group is online.

2 Repeat this command for all service groups that are online.

Closing VCS clientsExit all instances of the ClusterManager (Java Console), and ClusterManagementConsole (Single Cluster Mode) before the upgrade.

To close VCS clients

1 From the Cluster Manager (Java Console), click File > Logout on the ClusterExplorer window and then click File > Exit on the Cluster Monitor window.

2 For CMC, click Logout on the title bar of the Cluster Management Console.

Stopping VCS servicesStop the VCS services before the upgrade.

43Upgrading Veritas Cluster ServerUpgrading the VCS cluster to VCS 5.1 SP1

To stop VCS services

1 Stop HAD on all the cluster nodes. Type the following on the commandprompt:

C:\>hastop -all -force

2 Stop the Veritas Command Server service on all the cluster nodes. Type thefollowing on the command prompt:

C:\>net stop cmdserver

3 StopGABandLLTonall the clusternodes. Type the followingon the commandprompt:

C:\>net stop gab

C:\>net stop llt

4 If the Windows Indexing Service is installed, then type the following on thecommand prompt to stop this service:

C:\>net stop cisvc

Backing up customized type definitionsThe cluster type definitions are reset to their default values after the upgrade. Ifyou have modified the values of type definitions in the cluster, make a backupcopy of the types.cf file before the upgrade. The types.cf file is typically locatedat %VCS_HOME%\conf\config.

The variable %VCS_HOME% is the default installation directory for VCS, typicallyC:\Program Files\VERITAS\Cluster Server.

After you complete the upgrade, refer to the backup copy of the types.cf file anduse theClusterManager (JavaConsole) to change the type definition default valueswith the values you had originally set in the cluster.

Note: After the upgrade, do not replace the types.cf file with the backup copy.Use the backup copy only as a reference for the customized type definition valuesin the cluster.


44

SFW HA upgrade and Veritas NetbackupIf you are running Veritas NetBackup™ version 6.0 or 6.5 on systems where youare upgrading VCS then you must shut down the OpsCenterServer service priorto the upgrade.

BothNetBackupVCSand share the sameAT broker and client, and for this reasonthe OpsCenterServer service must by shut down prior to an upgrade.

Changing the driver signing optionsWhen upgrading on systems running Windows Server 2003, you must set theWindows driver signing option to ignore software authentication warningmessages.

To change the driver signing options

1 Open the Control Panel and click System.

2 Click the Hardware tab and click Driver Signing.

3 In the Driver Signing Options dialog box, note the current setting, and selectIgnore.

4 Click OK.

5 Repeat for each node in the cluster.

Note: If you donot change these options, the installer rejects the node at validationand halts the upgrade. After you complete the upgrading, you should reset thedriver signing options to their previous state.

Starting to upgrade the cluster to 5.1 SP1The product installer enables you to upgrade the cluster.

Make sure to select the same agents and options while upgrading the software. Ifyou do not want to include the enterprise agents and options in the upgradedcluster, uninstall the agents from the cluster before proceeding.

To upgrade the product using the installer

1 Allow the autorun feature to start the installation or double-click Setup.exe.

2 Choose the default language for your installation and click OK. The productselection screen appears.

3 Click Veritas Cluster Server 5.1 SP1 for Windows.

4 If asked, click Complete/Custom to begin installation, otherwise continue tothe next step.


5 Review the welcome message and click Next.

6 Review the terms of license agreement and, click Next.

7 Enter the product license key before adding license keys for features.

■ Enter the license key in the top field and click Add.

■ Repeat for additional license keys.

■ To remove a license key, click the key to select it and click Remove.

■ To see the license key's details, click the key.

■ Click Next.

8 Select the appropriate product options and click Next.

9 Select the appropriate installation options and click Next.

If any previous VCS agents and options are installed on the node, make sureyou select the same agents and options while upgrading. If you do not wantto include the agents and options in the upgraded cluster, uninstall themfrom the cluster before proceeding.

10 To install the client components on all the nodes in your installation, verifythat the check box is checked. Click Next.

11 Specify the domain and nodes for the upgrade.

■ Select the domain and thenode. These lists can take some time to populatedepending on domain and network size, speed, and activity.

■ To add a computer for installation, click Add. You can also type thecomputer’s name in the Computer field.To remove a computer, click the computer in the Selected Computers forInstallation field, and click Remove.

■ Repeat the above steps for each node.Click a computer’s name to see its description.

■ Click Next.

12 The installer checks the prerequisites for the selected computers anddisplaysthe results. Review the information and click Next.

Note that the Install Type for the nodes is listed asUpgrade. If an error occurs,address the problem described in the Details box.

13 If the installer has detected problems, review the messages, taking actionwhere necessary, and click Yes.

14 Review the information and click Install. Click Back to make changes.


46

15 If the installation is successful on all nodes, the installer automaticallyproceeds to the installation report. Click Next.

If an installation fails, click Next to review the report and address the reasonfor failure. You may have to either repair the upgrade or uninstall andre-install the upgrade to continue.

If a security alert asks you to accept the Veritas driver software, click Yes.

16 Reboot the remote nodes. Note that you cannot reboot the local node now,and that failed nodes are unchecked by default.

■ Click the check box next to the remote nodes that you want to reboot.

■ Click Reboot.

■ When the nodes have finished rebooting successfully, the Reboot Statusshows Online and the Next button is available.

■ Click Next.

17 Review the log files and click Finish.

18 Click Yes to reboot the local node.

After you upgrade the cluster to 5.1 SP1Perform the following after you upgrade the cluster to 5.1 SP1:

Resetting the driver signing optionsAfter completing the installation sequence, reset the drive signing options oneach computer.

Resetting the driver signing option procedure

1 Open the Control Panel, and click System.

2 Click the Hardware tab and click Driver Signing.

3 In the Driver Signing Options dialog box, reset the option to Warn or Block.

4 Click OK.

5 Repeat this procedure for each computer.

Reinstalling VCS Management Console 5.1If you uninstalled VCS Management Console earlier according to the proceduresfor preparing for the upgrade, you can now reinstall it.


To re-install VCS Management Console 5.1

1 Install VCS Management Console 5.1.

For information about installingVCSManagementConsole 5.1, see theVeritasCluster Server Management Console Implementation Guide.

2 Restore the backed up VCS Management Console 5.1 data files.

3 Start the VCSManagement Console. If themanagement console is clustered,bring the CMC_MS service group online.

Bringing the print share service group online after the upgradeFor VCS 5.1 SP1, the PrintSpool agent (for VCS) has been enhanced to meetscalability andperformance requirements. ThePrintSpool agentno longerdependson the RegRep agent for operation. The dependency between the PrintSpool andthe RegRep resource in a print share service group has been eliminated.

This affects print share service groups configured in earlier versions of VCS. Ifyou have configured a print share and you upgrade VCS, then the existing printshare service group will fail to come online, after the upgrade.

After the upgrade is complete, youmust run thePrint Share ConfigurationWizardto modify the print share service group. This will allow the wizard to make therequired changes to the service group configuration.

Note: In case of an upgrade, do not add or remove any resources, or modify anyother attributes in the print share service group for the first time you run thePrint Share Configuration Wizard to modify the service group.

Before you modify the existing print share service group:

■ Make sure that the VCS engine (HAD) is running on the cluster node.

■ Mount the drives or LUNs that contain the spooler and the registry replicationdirectories on the system on which you will run the wizard.

To modify the print share service group after an upgrade

1 Start thePrint ShareConfigurationWizard. (Start>AllPrograms>Symantec>VeritasClusterServer>ConfigurationTools>PrintShareConfigurationWizard)

2 Read the information on the Welcome panel and click Next.


48

3 On theWizardOptions panel, clickModifyservicegroup, select your existingprint share service group, and then click Next.

4 Click Next on the subsequent wizard panels and complete the wizard steps.You can now bring the printshare service group online.

Importing the VCS Management PackThis rollup patch contains fixes for the VCS Management Pack. If you havedeployed the VCS Management Pack for Microsoft Operations Manager 2005 inyour cluster environment, you can re-import the updated VCSManagement Packafter installing the rollup patch.

The updated VCS Management Pack is included with the rollup patch software.Import the appropriate VCS Management Pack (.akm file) using the MOM 2005SP1 Administrator Console.

While importing themanagement pack, ensure that you select theUpdateexistingManagement Pack option in the Management Pack Import/Export Wizard.

Changing the type definition default valuesThe cluster type definitions are reset to their default values after the upgrade.Refer to the backup copyof the types.cf file.Use theClusterManager (JavaConsole)to change the type definition default values with the values from the types.cfbackup file.

Note:Do not replace the types.cf file with the backup copy after the upgrade. Thebackup copy must be used only as a reference for the customized type definitionvalues in the cluster.

Upgrading an Exchange server clusterThis section describes the upgrade scenarios and upgrade tasks for upgrading toVCS 5.1 SP1 in an Exchange 2003 cluster.

During the upgrade you may want to update Exchange with a service pack afterupgrading VCS. For information on updating Exchange service packs,

See “Upgrading to Microsoft Exchange 2007 SP1 or SP2 in a VCS environment”on page 59.

See “Upgrading to Microsoft Exchange 2003 SP2 in a VCS environment”on page 58.

49Upgrading Veritas Cluster ServerUpgrading an Exchange server cluster

Upgrade scenariosTable 4-1 table presents possible scenarios for upgrading to a VCS 5.1 SP1 clusterwith Microsoft Exchange.

Table 4-1 Upgrade scenarios

Upgrade toUpgrade from

Exchangeserver version

OperatingSystem

VCS VersionExchangeserver version

OperatingSystem

VCSVersion

Exchange 2003(including theservice packs)

WindowsServer 2003

5.1SP1Exchange 2003WindowsServer2003

4.3, 5.0,5.0RP1a,5.1

Exchange 2007(including theservice packs)

WindowsServer 2003

5.1 SP1Exchange 2007WindowsServer2003

4.3,5.0RP2,5.1

Upgrade tasksPerform the following tasks to upgrade the Exchange server cluster:

■ Stop VCS services.See “Stopping VCS services” on page 43.

■ Upgrade VCS to version 5.1 SP1See “Upgrading the VCS cluster to VCS 5.1 SP1” on page 41.

Upgrading a SQL server clusterThis section provides information about upgrading toVCS 5.1 SP1 in a SQLServercluster.

During the cluster upgrade youmay alsowant to upgrade SQL Server 2000 to SQLServer 2005 or upgrade SQL Server 2000 or 2005 to SQL Server 2008.

See “Upgrading fromMicrosoft SQL Server 2000 to SQL Server 2005” on page 51.

See “Upgrading from Microsoft SQL Server 2000 or 2005 to SQL Server 2008”on page 54.

Additionally, you may want to update SQL Server with a service pack. Forinformation on upgrading SQL server service packs,

See “Upgrading Microsoft SQL 2000 to SP4 in a VCS environment” on page 62.

See “Upgrading Microsoft SQL 2005 to SP1 in a VCS environment” on page 64.

Upgrading Veritas Cluster ServerUpgrading a SQL server cluster

50

See “Upgrading Microsoft SQL 2005 to 2005 SP2 or later in a VCS environment”on page 65.

See “UpgradingMicrosoft SQL2008 to2008SP1 inaVCSenvironment”onpage69.

Note: If you are upgrading both Microsoft SQL Server and VCS, then you mustupgrade SQL Server first and then proceed with upgrading VCS.

Upgrade scenariosTable 4-2 presents possible scenarios for upgrading to a VCS 5.1 SP1 cluster withSQL Server.

Table 4-2 SQL cluster upgrade scenarios

Upgrade toUpgrade from

SQL 2000, SQL2005, SQL 2008

WindowsServer 2003

5.1SP1SQL 2000WindowsServer2003

4.3, 5.0 or5.0RP1a, 5.1

SQL 2005, SQL2008

WindowsServer 2003

5.1SP1SQL 2005WindowsServer2003

4.3, 5.0,5.0RP1a, 5.1

Upgrade tasksPerform the following tasks to upgrade the SQL Server cluster:

■ Stop the VCS services

■ Upgrade VCS to VCS 5.1 SP1

Upgrading from Microsoft SQL Server 2000 to SQL Server 2005Follow the sequence below toupgradeSQLServer 2000 to SQLServer 2005duringthe VCS upgrade to VCS 5.1 SP1.

■ Upgrade SQL Server on the first node.

■ Upgrade SQL Server on each additional node.

■ Create the SQL Server 2005 service group

■ Upgrade VCS 4.3, 5.0 or 5.0RP1a to VCS 5.1 SP1

51Upgrading Veritas Cluster ServerUpgrading a SQL server cluster

To upgrade SQL Server on the first node

1 Bring online the SQL 2000 service group resources up to the SQL Server 2000resource. Right-click each resource and select Online. Click Yes in theconfirmation pop-up to bring the resource online. This action brings onlinethe disks, volumes, and IP address associated with SQL Server.

2 Right-click the SQL Server service group in tree view and click Freeze>Persistent.

3 Back up the SQL Server 2000 (MSSQL) and Registry (RegRep) folders on theshared disk by making a copy of each.

4 Start SQL Server 2000 under a local node context. Click Start > Run and typeservices.msc.

5 In the Services panel, find MSSQLServer, right-click it, and select Start.

6 Launch the Microsoft SQL Server 2005 installer and proceed through theinstallation process.

Make sure that you select the option to upgrade the existing instance(s)whenprompted to do so. This action automatically places the data files in the properlocation.

Note: Depending on the circumstances, an in-place upgrade may not besuitable for your environment. Refer to Microsoft documentation beforebeginning any SQL Server upgrade.

7 Reboot the node if requested to do so when the installation completes.

8 Unfreeze and take offline the service group on the first node if you did notreboot. (Rebooting automatically takes the service group offline.)

Once you have completed the upgrade procedure on the first node, you mustperform the following steps on each additional node in the cluster.

To upgrade SQL Server on each additional node

1 Bring online the SQL 2000 service group resources up to the SQL Server 2000resource, but do not online the regrep resources. Right-click each resourceand select Online. Click Yes in the confirmation pop-up to bring the resourceonline.

2 Restore the copies of the SQL Server 2000 (MSSQL) and Registry (RegRep)folders on the shared disk. Delete the original MSSQL and RegRep folders.

3 Bring online the regrep resources (right-click and select Online).


52

4 In the treeview, freeze the service group (right-click and select Freeze >Persistent).

5 Start SQL Server 2000 under a local node context. Click Start > Run and typeservices.msc.

6 In the Services panel, find MSSQLServer, right-click it, and select Start.

7 Launch the Microsoft SQL Server 2005 installer and proceed through theinstallation process.

Make sure that you select the option to upgrade the existing instance(s)whenprompted to do so. This action automatically places the data files in the properlocation.

Refer to your Microsoft SQL Server 2005 documentation for more detailedinstructions on installing Microsoft SQL Server.

8 Reboot the node if requested to do so when the installation completes.

9 Unfreeze and take offline the service group on the secondary or additionalnode if you did not reboot. (Rebooting automatically takes the service groupoffline.)

Once you have completed upgrading all of the nodes in the SQL Server cluster,continue with creating the service group.

To create the SQL Server 2005 service group

1 On the first node, bring online the SQL Server resources from the SQL2000service group. Right-click the resource, select Online, and select the firstnode.

2 Delete the existingSQL2000 service group (in treeview). Right-click the servicegroup and selectDelete. ClickYeswhen asked to confirm if youwant to deletethe service group.

3 Create theSQL2005 service groupusing theSQLServerConfigurationWizard.Click Start>AllPrograms> Symantec> SQLServerConfiguration Wizard.

4 Test switch the service group to another node in the cluster. Right-click theservice group in treeview, select Switch To, and select any additional nodein the cluster.

Proceed with upgrading VCS. For details,

See “Upgrading the VCS cluster to VCS 5.1 SP1” on page 41.


Upgrading from Microsoft SQL Server 2000 or 2005 to SQL Server2008

The following steps describe how to upgrade your existing clustered SQL Server2000 or SQL Server 2005 setup to SQL Server 2008. Complete these steps on allthe cluster nodes that are part of the SQL service group, one node at a time.

Note: These steps are applicable only if you already have SQL 2000 or SQL 2005set up in a VCS 5.1 SP1 for Windows cluster environment.

At a high level, upgrading to SQL Server 2008 involves the following tasks:

■ Upgrade SQL Server on the first cluster node.

■ Upgrade SQL Server on each additional failover node.

■ In caseof aDisasterRecovery configuration, repeat theSQLupgradeprocedureson the nodes at the secondary site. First upgrade the first cluster node at theDR site, and then the additional failover nodes.

■ Delete the existing SQL2000 or 2005 service group, including the service groupat the DR site, if applicable.

■ Create a SQL Server 2008 service group using the SQL 2008 ConfigurationWizard. In case of aDR setup, create a service group at the secondary site also.

To configure a new HA and DR environment for SQL Server 2000 or SQL Server2005, refer to the Veritas Cluster Server Implementation Guide forMicrosoft SQL.

To configure a new HA and DR environment for SQL Server 2008, refer totheVeritas Cluster Server Implementation Guide for Microsoft SQL Server 2008.

Note: In case of a Disaster Recovery setup, you must first upgrade SQL on thecluster nodes at the primary site and thenproceedwith the nodes at the secondarysite. Youmust follow the same upgrade sequence at both sites, upgrade first nodeand then the additional nodes, as described in the procedures in this section.

Ensure that you perform the following before the upgrade:

■ Take a backup of the SQL databases.

■ In case of a Disaster Recovery environment, ensure that the databases on theprimary and secondary sites are synchronized and then stop the replicationbetween the sites.

■ Ensure that you have installedVCS 5.1 SP1 forWindows on all the SQL servicegroup cluster nodes that you wish to upgrade.


54

See “About installing VCS” on page 23.

■ Make anote of the SQLvirtual server nameand all the IP addresses configuredat both the primary and the secondary site, for the SQL setup in the DRenvironment. You will need these details later.

■ Make anote of the SQLvirtual server nameand all the IP addresses configuredat both the primary and the secondary site, for the SQL setup in the DRenvironment. You will need these details later.

Upgrading SQL on the first cluster nodeThese steps assume a single SQLServer instance configured in a two-node clusterconfiguration.

To upgrade SQL Server on the first cluster node

1 On the node on which the SQL service group is online, take all the resources(excluding the NetAppSnapDrive. Mount in case of Windows LDM) offline.Keep theNetAppSnapDrive (Mount in case ofWindowsLDM) resource online.

From the VCS Cluster Manager (Java Console), right-click the resource andselect Offline. Click Yes in the confirmation pop-up box to take the resourceoffline.

2 Bring the registry replication (RegRep) resource online.

3 Make a backup copy of the SQL Server 2000 or SQL Server 2005 and theRegistry (RegRep) directories from the shared disk and store them in atemporary location.

Youwill need the backed-updirectorieswhile upgradingSQLon the additionalfailover nodes, later.

4 Freeze the SQL Server service group.

From the VCS Cluster Manager (Java Console), right-click the SQL Serverservice group in tree view on the left pane, and click Freeze > Persistent.


5 Launch the Microsoft SQL Server 2008 installer and install SQL Server 2008on the node.Make sure that you select the option to upgrade the existing SQLServer instance(s), when prompted to do so. The SQL Server 2008 installerthen automatically places the SQL data files in the appropriate location.

Refer to the Microsoft SQL Server 2008 documentation for instructions.

6 Unfreeze and then take the SQL Server service group offline. From the VCSCluster Manager (Java Console), right-click the SQL Server service group intree view on the left pane and clickUnfreeze, and then take the entire servicegroup offline on the node.

This completes the upgrade steps on the first cluster node. Proceed toupgrading SQL on the additional failover nodes.

Upgrading SQL on the additional failover nodePerform the following steps on each additional failover node that is part of theSQL service group.

To upgrade SQL Server on the additional node

1 Bring all the SQL service group resources including the NetAppSnapDrive(Mount in case of Windows LDM) resource, online. From the VCS ClusterManager (Java Console), right-click the resource and select Online. Click Yesin the confirmation pop-up box to bring the resource online.

2 Rename the SQL Server and the Registry (RegRep) directories on the shareddisks. These directories are updated when SQL Server 2008 is install on thefirst node. You can also delete these directories, if desired.

3 Copy the backed-up SQL Server 2000 or SQL Server 2005 and the Registry(RegRep) directories from the temporary location to the shared disks. Thebackup directories are the same that you had backed up earlier whileupgrading SQL on the first cluster node.

4 Bring the RegRep resource online.

From the VCS Cluster Manager (Java Console), right-click the resource andselect Online. Click Yes in the confirmation pop-up box to bring the resourceonline.

5 Freeze the SQL service group.

From the VCS Cluster Manager (Java Console), right-click the SQL Serverservice group in tree view on the left pane and click Freeze > Persistent.


56

6 Launch the Microsoft SQL Server 2008 installer and install SQL Server 2008on the node.Make sure that you select the option to upgrade the existing SQLServer instance(s), when prompted to do so. The SQL Server 2008 installerthen automatically places the SQL data files in the appropriate location.

Refer to the Microsoft SQL Server 2008 documentation for instructions.

7 Unfreeze and then take the SQL Server service group offline. From the VCSCluster Manager (Java Console), right-click the SQL Server service group intree view on the left pane and clickUnfreeze, and then take the entire servicegroup offline on the node.

This completes the upgrade steps on the additional failover node. Proceed toconfiguring SQL service group in the cluster.

Configuring SQL service groupRun the SQLServer 2008ConfigurationWizard to configure the SQL2008 servicegroup on one of the cluster nodes at the primary site. Refer to the Veritas ClusterServer Implementation Guide for Microsoft SQL Server 2008 for instructions.

Note: In case of a Disaster Recovery setup, repeat these steps on the first clusternode at the secondary site and then reconfigure the DR components. Refer to theVeritas Cluster Server Implementation Guide for Microsoft SQL Server 2008 forinstructions.

To configure the SQL service group

1 Rename the Registry (RegRep) directory on the shared disk.

2 On the first cluster node, bring the NetAppFiler (DiskRes in case ofWindowsLDM) and NetAppSnapDrive (Mount in case of Windows LDM) resources ofthe SQL service group, online.

3 Delete the SQL service group.

From the VCS Cluster Manager (Java Console), right-click the SQL Serverservice group in tree view on the left pane and click Delete. Click Yes whenprompted to confirm if you want to delete the service group.

4 Create the SQL Server 2008 service group using the SQL Server 2008Configuration Wizard.

Refer to the Veritas Cluster Server Implementation Guide for Microsoft SQLServer 2008 for detailed instructions onhow to create the service group usingthe SQL Server 2008 Configuration Wizard.


5 After creating the SQL Server 2008 service group, verify the configurationby switching the service group to another node in the cluster.

6 Delete the RegRep directory that you renamed in the first step.

Upgrading the Microsoft service packsThis section describes how to upgrade Microsoft SQL and Microsoft Exchangeservers to their corresponding service packs. The outlined procedures areapplicable only if you already have your SQL or Exchange setup in a VCS clusterenvironment.

Upgrading to Microsoft Exchange 2003 SP2 in a VCS environmentThis section describes the procedure to upgrade the Microsoft Exchange 2003that is already configured in a VCS environment.

Using this procedure you can upgrade Exchange 2003 to Exchange 2003 SP2

Before upgrading to Microsoft Exchange 2003 SP2, make sure to set the"DetailMonitor" attribute of all "ExchService" type resources to zero.

Perform the following steps to upgrade an Exchange 2003 installation on a nodethat is part of the Exchange service group.Make sure that all the nodes which arepart of the Exchange service group have the same version and service pack levelof Microsoft Exchange.

To upgrade to Microsoft Exchange 2003 SP2

1 Make sure that you do not mount the Exchange databases on the failovernodes. Bring the Exchange service group online on the node where you areupgrading the Exchange installation.

2 Stop HAD on the node where the service group was brought online. At thecommand prompt, type:

C:\> hastop -local -force

3 Install Microsoft Exchange 2003 SP2 on the node where the service groupwas brought online.

If prompted to install the hotfix for Internet Information Services (IIS) 6.0,refer to the Microsoft Knowledge Base Article: 831464.

4 Start HAD on the node. At the command prompt, type:

C:\> hastart

Upgrading Veritas Cluster ServerUpgrading the Microsoft service packs

58

5 After the Exchange 2003 SP2 installation is complete, take the Exchangeservice group offline.

6 Restart the Windows Management Instrumentation (WMI) service from theServices snap-in.

7 Repeat step 1 through step 6 on all remaining nodes that are part of theExchange service group.

8 Update theExchConfig registry informationon every systemwhereExchangeis upgraded.

9 To update the registry on the local system, navigate to%vcs_home%\bin\ExchSetup folder and type the following at the commandprompt:

Setup.exe /UpdateExchVersion

10 To update the registry on more than one node simultaneously, navigate to%vcs_home%\bin\ExchSetup folder and type the following at the commandprompt:

Setup.exe /UpdateExchVersion system_name1 system_name2...

Here, system_name1, system_name2 are the cluster node names.

11 This completes the upgrade. You can now bring the Exchange service grouponline in the cluster.

12 For a disaster recovery environment, repeat this procedure at the secondary(DR) site.

Upgrading to Microsoft Exchange 2007 SP1 or SP2 in a VCSenvironment

This section describes how to upgrade Exchange 2007 to Exchange 2007 SP1 orSP2 using the Exchange 2007UpgradeWizard. It is applicable only if you alreadyhave Exchange 2007 set up in a VCS cluster environment.

To configure a new HA and DR environment for Exchange 2007, refer to thefollowing manual:

See theVeritasStorageFoundationandHighAvailability SolutionsHAandDisasterRecovery Solutions Guide for Microsoft Exchange 2007.

Before you proceed with the Exchange 2007 upgrade to SP1 or SP2, note thefollowing:

■ Ensure that the Exchange 2007 service group is offline in the cluster.

59Upgrading Veritas Cluster ServerUpgrading the Microsoft service packs

■ While performing the upgrade the Exchange 2007 Upgrade Wizard renamesand then restarts the cluster node. Exit all the other programs before you runthe wizard on a cluster node.

Note: The following procedure describes how to upgrade Exchange 2007 toExchange 2007 SP1, this procedure can also be used to upgrade Exchange 2007to Exchange 2007 SP2.

Complete the following steps on all cluster nodes that are part of the Exchange2007 service group, one node at a time.

To upgrade Exchange 2007 to Exchange 2007 SP1

1 On one of the cluster nodes, click Start>AllPrograms>Symantec>VeritasCluster Server > Configuration Tools > Exchange 2007 Upgrade Wizard tostart the Exchange 2007 Upgrade wizard.

2 Review the information on the Welcome panel and click Next.

3 On the Exchange Virtual Server Selection panel, select the Exchange virtualserver that you wish to upgrade and then click Next.

The Summary table provides the details of the Exchange virtual servers inthe cluster and their upgrade status on each cluster node.


60

4 The wizard performs the tasks required to set up the VCS environment forthe Exchange upgrade. The Tasks table displays the progress of the varioustasks. After all the tasks are completed, click Next.

5 Review the information on the Cluster Node Reboot panel and then clickReboot. The wizard prompts you to reboot the node. Click Yes to reboot thenode.

TheExchange virtual server name is temporarily assigned to the cluster node.On rebooting the node, the Exchange 2007 Upgrade Wizard is launchedautomatically with a message that the Exchange pre-upgrade tasks arecomplete. Do not click Continue at this time. Wait until after the Exchangeupgrade is complete.

6 Run the Exchange 2007 SP1 installer to upgrade Exchange 2007 on the node.Type the following at the command prompt:

<drive letter>:\setup.com /mode:Upgrade

Here <drive letter> is the drivewhere theExchange SP1 installer is located.

Note: You can also run Setup.exe to launch the installer GUI for upgradingExchange. If using the installer GUI, ensure that you do not select any otherExchange 2007 server role. Only the Mailbox server role must be upgraded.

Verify that the upgrade has completed successfully. In case there are errorsor if the upgrade has partially succeeded or has failed, resolve the errors andensure that the upgrade is successful.

Refer to the Microsoft Exchange documentation for more information.

7 Return to the Exchange 2007 Upgrade Wizard and click Continue.

If thewizard is not running, click Start>AllPrograms>Symantec>VeritasCluster Server > Configuration Tools > Exchange 2007 Upgrade Wizard tostart the wizard and then click Next.

8 The wizard performs the tasks required to set up the VCS environment afterthe Exchange upgrade. The Tasks table displays the progress of the varioustasks. After all the tasks are completed, click Next.

9 Review the information on the completion panel and then click Finish.

The wizard displays the status of the Exchange virtual server upgrade. TheSummary table provides the details of the Exchange virtual servers in thecluster and their upgrade status on each cluster node.


10 Repeat these steps on the remaining cluster nodes. After you have upgradedall the cluster nodes that are configured to host the Exchange virtual server,bring the Exchange 2007 service group online in the cluster.

Note: Do not bring the Exchange 2007 service group online until you havecompleted the upgrade on all the cluster nodes that are part of the servicegroup.

11 For a disaster recovery environment, repeat this procedure at the secondary(DR) site.

Upgrading Microsoft SQL 2000 to SP4 in a VCS environmentThis section describes how to upgrade SQL 2000 to SQL 2000 SP4. It is applicableonly if you already have SQL 2000 set up in a VCS cluster environment.

Consider the following points before applying Microsoft SQL 2000 SP4 to aproduction server:

■ Review your Microsoft documentation for the requirements for a MicrosoftSQL 2000 Server SP4 installation.Make sure your system meets these requirements.

■ Make sure that you have a recent backup of your system and user databases.

■ Server down time is required for this procedure.

To install Microsoft SQL 2000 Server SP4

1 From theCluster Explorer, right-click the SQLServer service group and selectOffline on all nodes.

2 On the node where the SQL Server service group was taken offline, onlinethe MountV resource for the shared drive containing the SQL databases (forexample, S:\MSSQL$SQL2000).

3 On the shared disk, make a copy of your recent MSSQL data files directory(S:\MSSQL$SQL2000) and rename it, for example to S:\MSSQL$2000.SP3A.

4 From the Cluster Explorer, right-click the SQL Server service group which isnow partially online, and select Freeze >Persistent.

5 Install Microsoft SQL 2000 Service Pack 4 on the active node (where the SQLServer service group is online), using the instructions provided byMicrosoft.

6 Repeat step 5 for each additional SQL instance in this service group, if youhave more than one instance in this service group.


62

7 From the Cluster Explorer, right-click the SQL Server service group which isstill online and select Unfreeze.

8 From theCluster Explorer, right-click the SQLServer service group and selectOffline on the node where it was online.

9 In a Disaster Recovery environment, switch the Replication service group toone of the other additional or failover nodes in this cluster.

10 On the failover node, online the MountV resource for the shared drivecontaining the SQL databases (for example, S:\MSSQL$SQL2000).

11 On the shared disk, rename the S:\MSSQL$SQL2000 directory toS:\MSSQL$SQL2000.SP4. If S:\MSSQL$SQL2000.SP4 already exists on theshareddisk, thendelete it before renaming theS:\MSSQL$SQL2000directory.

12 On the shared disk, rename the S:\MSSQL$SQL2000.SP3A directory toS:\MSSQL$SQL2000. If there are additional nodes in this cluster to beupdated,copy the S:\MSSQL$SQL2000.SP3Adirectory to S:\MSSQL$SQL2000 insteadof renaming the directory.

13 From the Cluster Explorer, right-click the SQL Server service group which isnow partially online and select Freeze >Persistent.





18 Repeat step 9 through step 17 on each additional node if more than two SQL2000 nodes are in use.

19 For aDisaster Recovery environment, repeat this procedure at the secondarysite.

20 WhenMicrosoft SQL2000Server ServicePack4has been completely installedon all nodes, test user connectivity to the instances.

21 Test the SQL Server service group by bringing it online and failing it overfrom node to node. When testing is complete, the upgrade is complete.

22 If more than one SQL Server service group is present, repeat this entireprocedure for each SQL Server service group.


Upgrading Microsoft SQL 2005 to SP1 in a VCS environmentThis section describes how to upgrade SQL 2005 to SQL 2005 SP1. It is applicableonly if you already have SQL 2005 set up in a VCS cluster environment.

Consider the following points before applying Microsoft SQL 2005 Server SP1 toa production server:

■ Review your Microsoft documentation for the requirements for a MicrosoftSQL 2005 Server SP1 installation.Make sure your system meets these requirements.


■ Server down time is required for this procedure.

To install Microsoft SQL 2005 Server SP1

1 From theCluster Explorer, right-click the SQLServer service group and selectOffline on all nodes.

2 On the node where the SQL Server service group was taken offline, onlinethe SQL 2005 resource for the shared drive containing the SQL databases.

3 From the Cluster Explorer, right-click the SQL Server service group which isnow partially online, and select Freeze >Persistent.

4 If a VVR RVG service group is present, verify that it is online on the nodewhere Microsoft SQL 2005 Service Pack 1 is to be installed.





9 On the failover node, online the SQL 2005 resource for the shared drivecontaining the SQL databases.

10 From the Cluster Explorer, right-click the SQL Server service group which isnow partially online and select Freeze >Persistent.

11 Install Microsoft SQL 2005 Service Pack 1 on the active node (where the SQLServer service group is online), using the instructions provided by MicrosoftSQL Server 2005 Service Pack 1 Setup.


64


13 From the Cluster Explorer, right-click the SQL Server service group which isstill online and select Unfreeze

14 From theCluster Explorer, right-click the SQLServer service group and selectOffline on the node where it was online

15 Optionally reboot andonline each service group to verify the database connectfor each node.

16 Repeat step 9 through step 17 on each additional node if more than two SQL2005 nodes are in use.

17 For aDisaster Recovery environment, repeat this procedure at the secondarysite.

18 WhenMicrosoft SQL2005Server ServicePack1has been completely installedon all nodes, test user connectivity to the instances.

19 Test the SQL Server service group by bringing it online and failing it overfrom node to node. When testing is complete, the upgrade is complete.

20 If more than one SQL Server service group is present, repeat this entireprocedure for each SQL Server service group.

Upgrading Microsoft SQL 2005 to 2005 SP2 or later in a VCSenvironment

This section describes how to upgrade SQL 2005 to SQL 2005 SP2 or later. It isapplicable only if you already have SQL 2005 set up in aVCS cluster environment.

Note: Do not follow the installation steps provided in this section to install SQLServer 2005 Service Pack 1 and all other hotfixes released before Service Pack 2.

PrerequisitesConsider the following points before applying Microsoft SQL 2005 Server SP2 orlater service pack version to a production server:

■ You must be a domain user having administrative privileges to the clusternodes.

■ You must have administrative privileges to the SQL instance that you wish toupgrade.

■ You must back up the SQL Server 2005 databases.


■ Refer to the Microsoft documentation for prerequisites related to SQL Server2005 Service Pack installation.

Preliminary installation informationTypically,multiple SQL instances are configured in aVCS cluster. EachSQL servicegroup is configured to fail over on one or more nodes in the cluster. The node onwhich the SQL service group is online is called as the Active node for that SQLinstance. Thenode onwhich the SQL service group is offline is called as thePassivenode for that SQL instance. The procedure for applying service packs, patches,or hotfixes for SQL instances varies depending on whether it is an active or apassive node. This document describes procedures for both the cases in detail.

Use the procedure that applies to the type of setup you have.

Toprovide context, the installationprocedures described in this document assumetwo SQL Server 2005 instances configured in a three-node VCS cluster.

Table 4-3 lists the configuration objects referenced in the following procedures.

Table 4-3 SQL Server 2005 SP upgrade configuration objects

DescriptionObject

Cluster node namesNode1, Node2, Node3

SQL Server 2005 instance namesSQLinst1, SQLinst2

SQL Server 2005 SP2 installer for 32-bitSQLServer2005SP2-KB921896-x86-ENU.exe

The configuration is as follows:

■ SQLinst1 can fail over on Node1 and Node2, and SQLinst2 can fail over onNode3 and Node2.So, Node2 is the common failover node for SQLinst1 and SQLinst2.

■ The SQL service group for SQLinst1 is online on Node1, and the SQL servicegroup for SQLinst2 is online on Node3.So, Node1 and Node3 are the “active” nodes for SQLinst1 and SQLinst2respectively. Node2 is the “passive” node for both SQL instances.Wewill first install the service pack onNode2 (passive node) and then proceedto install on Node1 and Node3.

Installing the Service Pack on “passive” cluster nodesPerform these steps on all the nodes where the SQL service group is configuredto fail over but is not online. You can either perform the installation at one time


66

for all the SQL instances that are configured to fail over on the node, or repeatthe steps for each SQL instance separately.

Do not run these steps for SQL instances whose corresponding service groups areonline on the nodes (active nodes). For installation on active nodes,

See “Installing the Service Pack on “active” cluster nodes” on page 68.

Note: You can install SQL Server 2005 Service Pack in an unattended mode fromthe command prompt using the /quiet switch to suppress the setup dialog boxes.Refer to the Microsoft documentation for more information.

To install the Service Pack on passive cluster nodes

1 Ensure that service groups for SQL instances SQLinst1 and SQLinst2 areoffline on Node2.

Note: This upgrade procedure will not upgrade the SQL instance whosecorresponding service group is online on the node.

2 On Node2, copy the SQL Server 2005 Service Pack installer or map a drive tothe directory where the installer is located.

3 From the command prompt on Node2, navigate to the directory where theinstaller is located.

4 From the command prompt, run the Service Pack installer command withthe appropriate options.

For example,

The command format for running the installer is as follows:

SQLServer2005SP2-KB921896-x86-ENU.exe [options] /passive=1

You can use the following options for the command:

■ /allinstancesThis option upgrades all SQL Server 2005 instances and sharedcomponents to the desired SQL Server 2005 SP.

■ /instancename = “<instance1>, <instance2>, ...”This option upgrades only the specified SQL Server 2005 instances andshared components to the desired SQL Server 2005 SP.

You can run any of the following commands on Node2:

SQLServer2005SP2-KB921896-x86-ENU.exe /allinstances /passive=1


or

SQLServer2005SP2-KB921896-x86-ENU.exe /instancename = SQLinst1,

SQLinst2 /passive=1

Note that in case ofmultiple SQL instances, there should beno spaces betweeninstance names in the command.

5 Follow the upgrade wizard to complete the installation.

Once the installation is complete on the passive nodes, proceed to install onthe active nodes.

Installing the Service Pack on “active” cluster nodesPerform these steps on all the nodes on which the SQL service group is online.You can either perform the installation at one time for all the SQL instances thatare configured to fail over and are online on the node, or repeat the steps for eachSQL instance separately.

Do not run these steps for SQL instances whose corresponding service groups areoffline on the nodes (passive nodes). For installation on passive nodes,

See “Installing the Service Pack on “passive” cluster nodes” on page 66.

Referring to the configuration example described earlier, run these steps onNode1and Node3 where the SQL service groups for SQLinst1 and SQLinst2 are online.

To install the Service Pack on active cluster nodes

1 Ensure that the SQL service group for SQLinst1 is online on Node1.

2 In the SQL service group for SQLinst1, take all resources of typeSQLServer2005 offline on Node1.

If there are other SQL Server 2005 instances configured on the node that youwish to upgrade, take SQLServer2005 resources of the respective servicegroups offline as well.

3 From the Services snap-in, stop the SQL server Full Text Search service andthe Analysis service, if they are not configured as part of the SQL servicegroups.

4 Freeze the SQL service group for SQLinst1 on Node1.

From the Cluster Manager (Java Console), right-click the SQL service group,select Freeze and click Temporary.

or

Type the followingon the commandprompt: hagrp -freeze service_group


68

5 If the SQL Server Reporting Services is installed for a particular instance,start the SQL Server Database Service of the respective instance using theServices snap-in.

6 Run the SQL Server 2005 Service Pack installer.

Double-click SQLServer2005SP2-KB921896-x86-ENU.exe to launch the SPinstallation wizard.

7 Follow the upgrade wizard to complete the installation.

8 After the installation is complete, stop the SQL Server services, if startedbefore applying the patch.

Note: SQLServer2005 resources may go in UNKNOWN state if we start theservices outside the VCS cluster. Ignore this and probe the resources afterinstallation is completed and all the services are stopped.

9 Unfreeze the SQL service group and probe the resources for SQLinst1 onNode1.

From the Cluster Manager (Java Console), right-click the SQL service group,select Unfreeze.

or

Type the following on the command prompt: hagrp -unfreeze

service_group

10 From the Services snap-in, start the SQL server Full Text Search service andthe Analysis service, if they are not configured as part of the SQL servicegroups.

11 Ensure that all the services related to the SQL Server 2005 instance are instopped state

12 Apart fromtheSQLBrowser service, set the startup type of all theSQL servicesto manual.

13 Bring the SQLServer2005 resources in the SQL service group for SQLinst1online on Node1.

14 Repeat step 1 to step 13 for SQLinst2 on Node3.

Upgrading Microsoft SQL 2008 to 2008 SP1 in a VCS environmentThis section discusses the procedure to upgradeMicrosoft SQL 2008 toMicrosoftSQL 2008 SP1 in a VCS 5.1 SP1 environment.


The procedure is applicable only if you already have SQL 2008 set up in a VCScluster environment.

Prerequisites for upgrading toMicrosoft SQL Server 2008 SP1Consider the following points before proceeding with the upgrade:

■ You must have administrative privileges to the SQL instance that you wish toupgrade.


■ Make sure that the VCS version installed is VCS 5.1 SP1.

■ Refer to the Microsoft documentation for prerequisites related to SQL Server2008 Service Pack 1 installation.

Upgrading to Microsoft SQL Server 2008 SP1The following upgrade procedure considers a two node cluster, Node A and NodeB.

The SQL service group is ONLINE on Node A, and Node B is the passive node.

Upgrading from Microsoft SQL 2008 to Microsoft SQL Server 2008 SP1

1 Change theRegRep resource ExcludeKeysAttribute on anyone of the clusternodes, using HA commands or JavaGUI.

Add the following key in Exclude Keys:

HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\

InstanceName\MSSQLServer\Filestream

2 Upgrade the SQL 2008 instance on Node B ( passive node) and reboot NodeB.

Note: Upgrade to SQL 2008 SP1 requires a reboot if you are upgrading forfirst time.

3 Proceed to failover the Service Group from Node A to Node B.

4 Ensure that all services are coming online and working as expected.

Check the SQL version.


70

5 Upgrade the SQL2008 instance onNodeA. After a reboot, failover the ServiceGroup and repeat step 4 .

6 Remove the Exclude key from RegRep resource that was added in step 1.



72

Services and ports used byVCS

This appendix includes the following topics:

■ About VCS services and ports

About VCS services and portsIf youhave configured theWindows firewall, then ensure that the firewall settingsallow access to the services or ports used by VCS.

Table A-1 displays the services and ports used by VCS .

Note: The following port numbers that appear in bold are mandatory forconfiguring VCS: 2148, 14150, 14141, and 7419.

Table A-1 VCS services and ports

ProcessDescriptionProtocolPort Number

cmdServer.exeVeritas Command ServerTCP14150

had.exeVeritas High Availability Engine

Veritas Cluster Manager (Javaconsole) (ClusterManager.exe)

VCS Agent driver(VCSAgDriver.exe)

TCP14141

AAppendix

Table A-1 VCS services and ports (continued)


pluginHost.exeSymantec Plugin Host Service

Solutions Configuration Center(SFWConfigPanel.exe)

CCF Engine (CEngineDriver.exe)

TCP7419

pbx_exchange.exeSymantec Private BranchExchange

TCP/UDP1556

vxatd.exeSymantec ProductAuthentication Service (VxSS)

TCP/UDP2821

vras.dllVolume ReplicatorAdministrative Service

TCP8199

vxio.sysVCS Cluster HeartbeatsUDP4145

VxSchedService.exeVeritas Scheduler Service

Use to launch the configuredschedule.

TCP4888

User configurableports created at kernellevel by vxio .sys file

Volume Replicator PacketsTCP/UDP49152-65535

vrtsweb.exeVCS Secure Web ServerTCP8443

Notifier.exeVCS NotificationTCP/UDP14144

hasim.exeVCS Cluster SimulatorTCP/UDP14153, 15550- 15558

wac.exeVCSGlobal Cluster Option (GCO)TCP/UDP14155

vrtsweb.exeVRTS Web AdministrationTCP/UDP8181/ 8443/14151

xprtld.exeVeritas Storage FoundationMessaging Service

HTTPS5634

Services and ports used by VCSAbout VCS services and ports

74

Table A-1 VCS services and ports (continued)


cmcweb.exeVeritas Cluster ServerManagementConsoleWebServer

MS port: 14145

Sybase ASA port: 14994

HTTPS Web Server: 14443

For informationabout theVeritasCluster Server ManagementConsole and ports, see theVeritas™ Cluster ServerManagement ConsoleImplementation Guide.

TCP/UDP14145 1499414443

75Services and ports used by VCSAbout VCS services and ports

Services and ports used by VCSAbout VCS services and ports

76

AAfter installing 26After upgrading to 5.1 SP1 47

changing the type definition default values 49importing the VCS management pack 49

BBefore installing 24Before upgrading to 5.1 SP1

changing the driver signing options 45general preparations 42

Browsers supported 11

Ffeatures

adding 31removing 31

firewalls 73

Gglobal clusters 21

HHardware requirements 9

Iinstallation

adding or removing features 31license management 19repairing 30

Installation planning 19Installation requirements 9Installing

using product installer 23VCS 24

Installing VCSusing command line 27

Llicensing 18

adding or removing 19management 19

MMicrosoft Exchange 2003

service pack 2configuring in a VCS environment 58

Microsoft Exchange 2007service pack 1

configuring in a VCS environment 59Modifying driver signing options 24

NNetwork requirements 10notification

configuring SFW HA 21

Pports used by SFW HA 73print share service group

bringing online after upgrade 48product installer

uninstalling 35

RRecovery tools 22repairing the installation 30Requirements

hardware 9installation 9network 10

Resetting the driver signing options 26

Sservice pack upgrades

Microsoft Exchange 2003 SP2 58Microsoft Exchange 2007 SP1 59

Index

service pack upgrades (continued)Microsoft SQL 2000 SP4 62Microsoft SQL 2005 SP1 64

setup.exe parametersnode 37Reboot 37Solution 37

SFW HAconfiguring

notification 21services and ports used by 73

Starting to upgrade to 5.1 SP1 45Supported

browsers 11Microsoft Exchange servers and the

corresponding operating systems 13Microsoft SQL servers and the corresponding

operating systems 13Network Appliance applications 17Operating systems 12operating systems and application versions 12Oracle versions and the correspondingoperating

systems 16Symantec Product Authentication Service 19

Uuninstalling

using command line 37using product installer 35

UpdateVCS components 31

UpgradeExchange server cluster 49

upgrade scenarios 50Microsoft 2000 to SP4 62Microsoft SQL 2008 to 2008 SP1 69SQL 2005 to 2005 SP2 or later 65SQL Server 2000 or 2005 to SQL Server 2008 54

Configuring SQL service group 57SQL Server 2000 or 2005 to SQL Server 2008 on

the additional failover node 56SQL Server 2000 or 2005 to SQL Server 2008 on

the first node 55SQL Server 2000 to SQL Server 2005 51SQL Server Cluster

upgrade tasks 51SQL Server cluster 50

Upgrade scenarios 51

upgrading SFW HAbring print share service group online 48

Upgrading the cluster to 5.1 SP1 41

VVeritas Cluster Server Management Console 20

Index78

Date post:	03-Feb-2022
Category:	Documents
Upload:	others
View:	7 times
Download:	0 times

Veritas Cluster Server 5.1 SP1 Installation and Upgrade Guide

Documents