Symantec™ Storage Foundation 6.2 Installation Guide - Linux

Add to my manuals
219 Pages

advertisement

Symantec™ Storage Foundation 6.2 Installation Guide - Linux | Manualzz

Symantec™ Storage

Foundation 6.2 Installation

Guide - Linux

March 2015

Symantec™ Storage Foundation Installation Guide

The software described in this book is furnished under a license agreement and may be used only in accordance with the terms of the agreement.

Product version: 6.2

Document version: 6.2 Rev 2

Legal Notice

Copyright © 2015 Symantec Corporation. All rights reserved.

Symantec, the Symantec Logo, the Checkmark Logo, Veritas, Veritas Storage Foundation,

CommandCentral, NetBackup, Enterprise Vault, and LiveUpdate are trademarks or registered trademarks of Symantec Corporation or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners.

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

Corporation and its licensors, if any.

THE DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED

CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED

WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR

NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH

DISCLAIMERS ARE HELD TO BE LEGALLY INVALID. SYMANTEC CORPORATION SHALL

NOT BE LIABLE FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES IN CONNECTION

WITH THE FURNISHING, PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE

INFORMATION CONTAINED IN THIS DOCUMENTATION IS SUBJECT TO CHANGE

WITHOUT NOTICE.

The Licensed Software and Documentation are deemed to be commercial computer software as defined in FAR 12.212 and subject to restricted rights as defined in FAR Section 52.227-19

"Commercial Computer Software - Restricted Rights" and DFARS 227.7202, "Rights in

Commercial Computer Software or Commercial Computer Software Documentation", as applicable, and any successor regulations, whether delivered by Symantec as on premises or hosted services. Any use, modification, reproduction release, performance, display or disclosure of the Licensed Software and Documentation by the U.S. Government shall be solely in accordance with the terms of this Agreement.

Symantec Corporation

350 Ellis Street

Mountain View, CA 94043 http://www.symantec.com

Technical Support

Symantec Technical Support maintains support centers globally. Technical Support’s primary role is to respond to specific queries about product features and functionality.

The Technical Support group also creates content for our online Knowledge Base.

The Technical Support group works collaboratively with the other functional areas within Symantec to answer your questions in a timely fashion. For example, the

Technical Support group works with Product Engineering and Symantec Security

Response to provide alerting services and virus definition updates.

Symantec’s support offerings include the following:

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

Telephone and/or Web-based support that provides rapid response and up-to-the-minute information

Upgrade assurance that delivers software upgrades

Global support purchased on a regional business hours or 24 hours a day, 7 days a week basis

Premium service offerings that include Account Management Services

For information about Symantec’s support offerings, you can visit our website at the following URL: www.symantec.com/business/support/index.jsp

All support services will be delivered in accordance with your support agreement and the then-current enterprise technical support policy.

Contacting Technical Support

Customers with a current support agreement may access Technical Support information at the following URL: www.symantec.com/business/support/contact_techsupp_static.jsp

Before contacting Technical Support, make sure you have satisfied the system requirements that are listed in your product documentation. Also, you should be at the computer on which the problem occurred, in case it is necessary to replicate the problem.

When you contact Technical Support, please have the following information available:

Product release level

Hardware information

Available memory, disk space, and NIC information

Operating system

Version and patch level

Network topology

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 registration

If your Symantec product requires registration or a license key, access our technical support Web page at the following URL: www.symantec.com/business/support/

Customer service

Customer service information is available at the following URL: www.symantec.com/business/support/

Customer Service is available to assist with non-technical questions, such as the following types of issues:

Questions regarding product licensing or serialization

Product registration updates, such as address or name changes

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

Latest information about product updates and upgrades

Information about upgrade assurance and support contracts

Information about the Symantec Buying Programs

Advice about Symantec's technical support options

Nontechnical presales questions

■ Issues that are related to CD-ROMs or manuals

Support agreement resources

If you want to contact Symantec regarding an existing support agreement, please contact the support agreement administration team for your region as follows:

Asia-Pacific and Japan

Europe, Middle-East, and Africa

North America and Latin America [email protected]

[email protected]

[email protected]

Documentation

Product guides are available on the media in PDF format. Make sure that you are using the current version of the documentation. The document version appears on page 2 of each guide. The latest product documentation is available on the Symantec website.

https://sort.symantec.com/documents

Your feedback on product documentation is important to us. Send suggestions for improvements and reports on errors or omissions. Include the title and document version (located on the second page), and chapter and section titles of the text on which you are reporting. Send feedback to: [email protected]

For information regarding the latest HOWTO articles, documentation updates, or to ask a question regarding product documentation, visit the Storage and Clustering

Documentation forum on Symantec Connect.

https://www-secure.symantec.com/connect/storage-management/ forums/storage-and-clustering-documentation

About Symantec Connect

Symantec Connect is the peer-to-peer technical community site for Symantec’s enterprise customers. Participants can connect and share information with other product users, including creating forum posts, articles, videos, downloads, blogs and suggesting ideas, as well as interact with Symantec product teams and

Technical Support. Content is rated by the community, and members receive reward points for their contributions.

http://www.symantec.com/connect/storage-management

Contents

Technical Support

............................................................................................... 4

Section 1 Installation overview and planning

.................. 14

Chapter 1

Chapter 2

Chapter 3

Chapter 4

Introducing Storage Foundation

...................................... 15

About Storage Foundation .............................................................. 15

About Symantec Replicator Option ............................................. 16

About Veritas Operations Manager ................................................... 16

About Symantec Operations Readiness Tools .................................... 16

System requirements

......................................................... 19

Release notes ............................................................................. 19

Important preinstallation information for SF ........................................ 20

Supported operating systems .......................................................... 20

Storage Foundation memory requirements ........................................ 20

Disk space requirements ................................................................ 20

Checking installed product versions and downloading maintenance releases and patches .............................................................. 20

Obtaining installer patches ............................................................. 22

Disabling external network connection attempts .................................. 23

Database requirements ................................................................. 23

VxVM licenses ............................................................................. 23

Cross-Platform Data Sharing licensing .............................................. 24

Planning to install Storage Foundation

.......................... 25

About planning for SF installation ..................................................... 25

About installation and configuration methods ...................................... 26

About response files ............................................................... 27

Downloading the Storage Foundation software ................................... 28

Licensing Storage Foundation

.......................................... 30

About Symantec product licensing ................................................... 30

Setting or changing the product level for keyless licensing .................... 31

Contents 8

Installing Symantec product license keys ........................................... 33

Section 2 Installation of Storage Foundation

................... 35

Chapter 5

Chapter 6

Chapter 7

Chapter 8

Chapter 9

Preparing to install Storage Foundation

........................ 36

Installation preparation overview ...................................................... 36

About using ssh or rsh with the installer ............................................ 37

Setting environment variables ......................................................... 37

Mounting the product disc .............................................................. 38

Assessing the system for installation readiness .................................. 39

Prechecking your systems using the installer ............................... 39

Installing Storage Foundation using the script-based installer

................................................... 41

About the script-based installer ....................................................... 41

Installing Storage Foundation using the script-based installer ................ 43

Installing Storage Foundation using the web-based installer

........................................................................... 47

About the web-based installer ......................................................... 47

Before using the web-based installer ................................................ 48

Starting the web-based installer ....................................................... 48

Obtaining a security exception on Mozilla Firefox ................................ 49

Performing a preinstallation check with the web-based installer .............. 50

Installing SF with the web-based installer .......................................... 50

Automated installation using response files

................. 53

Installing SF using response files ..................................................... 53

Response file variables to install Storage Foundation ........................... 54

Sample response file for SF installation ............................................. 56

Configuring SF using response files ................................................. 57

Response file variables to configure Storage Foundation ...................... 57

Installing Storage Foundation using operating system-specific methods

............................................. 60

About installing SF using operating system-specific methods ................. 60

Installing SF using Kickstart ............................................................ 61

Sample Kickstart configuration file ................................................... 62

Installing Storage Foundation using yum ........................................... 64

Contents 9

Chapter 10

Installing SF using the Red Hat Satellite server ................................... 69

Using Red Hat Satellite server to install SF products ...................... 70

Configuring Storage Foundation

..................................... 72

Configuring Storage Foundation using the installer .............................. 72

Configuring Storage Foundation manually ......................................... 72

Configuring Veritas Volume Manager .......................................... 73

Configuring Veritas File System ................................................. 73

Configuring SFDB ........................................................................ 74

Section 3 Managing your Symantec deployments

............................................................. 75

Chapter 11 Performing centralized installations using the

Deployment Server

....................................................... 76

About the Deployment Server ......................................................... 77

Deployment Server overview .......................................................... 78

Installing the Deployment Server ..................................................... 79

Setting up a Deployment Server ...................................................... 80

Setting deployment preferences ...................................................... 83

Specifying a non-default repository location ....................................... 85

Downloading the most recent release information ............................... 85

Loading release information and patches on to your Deployment

Server .................................................................................. 86

Viewing or downloading available release images ............................... 87

Viewing or removing repository images stored in your repository ............ 92

Deploying Symantec product updates to your environment ................... 94

Finding out which releases you have installed, and which upgrades or updates you may need ............................................................ 95

Defining Install Bundles ................................................................. 97

Creating Install Templates ............................................................ 102

Deploying Symantec releases ....................................................... 104

Connecting the Deployment Server to SORT using a proxy server ................................................................................. 107

Contents 10

Section 4 Upgrade of SF

.............................................................. 108

Chapter 12

Chapter 13

Chapter 14

Chapter 15

Planning to upgrade SF

.................................................... 109

Upgrade methods for SF .............................................................. 109

Supported upgrade paths for SF 6.2 ............................................... 110

About using the installer to upgrade when the root disk is encapsulated ....................................................................... 113

Preparing to upgrade SF .............................................................. 114

Getting ready for the upgrade .................................................. 114

Creating backups ................................................................. 115

Determining if the root disk is encapsulated ................................ 116

Pre-upgrade tasks for migrating the SFDB repository database ...................................................................... 117

Pre-upgrade planning for Volume Replicator .............................. 117

Upgrading the array support ................................................... 120

Using Install Bundles to simultaneously install or upgrade full releases

(base, maintenance, rolling patch), and individual patches ............ 120

Upgrading Storage Foundation

...................................... 123

Upgrading Storage Foundation from previous versions to 6.2 ............... 123

Upgrading Storage Foundation using the script-based installer ......................................................................... 123

Upgrading SF using the web-based installer ..................................... 127

Upgrading Volume Replicator ........................................................ 129

Upgrading VVR without disrupting replication ............................. 129

Upgrading SFDB ........................................................................ 130

Performing an automated SF upgrade using response files

............................................................... 132

Upgrading SF using response files ................................................. 132

Response file variables to upgrade Storage Foundation ..................... 133

Sample response file for SF upgrade .............................................. 135

Migrating from Storage Foundation Basic to Storage

Foundation Standard

.................................................. 137

Migrating from Storage Foundation Basic to Storage Foundation

Standard ............................................................................. 137

Contents 11

Chapter 16 Performing post-upgrade tasks

...................................... 140

Optional configuration steps .......................................................... 140

Re-joining the backup boot disk group into the current disk group ......... 141

Reverting to the backup boot disk group after an unsuccessful upgrade .............................................................................. 141

Post upgrade tasks for migrating the SFDB repository database ........... 142

Migrating from a 5.0 repository database to 6.2 ........................... 142

Migrating from a 5.1 or higher repository database to 6.2 .............. 145

Migrating SFDB from 5.0x to 6.2 .............................................. 147

Recovering VVR if automatic upgrade fails ....................................... 147

Upgrading disk layout versions ...................................................... 148

Upgrading VxVM disk group versions .............................................. 149

Updating variables ...................................................................... 149

Setting the default disk group ........................................................ 149

Verifying the Storage Foundation upgrade ....................................... 150

Section 5 Post-installation tasks

............................................ 151

Chapter 17

Chapter 18

Performing post-installation tasks

................................ 152

Switching on Quotas ................................................................... 152

Enabling DMP support for native devices ......................................... 152

About configuring authentication for SFDB tools ................................ 153

Configuring vxdbd for SFDB tools authentication ......................... 153

Verifying the SF installation

............................................ 155

Verifying that the products were installed ......................................... 155

Installation log files ...................................................................... 156

Using the installation log file .................................................... 156

Using the summary file .......................................................... 156

Starting and stopping processes for the Symantec products ............... 156

Checking Veritas Volume Manager processes .................................. 157

Section 6 Uninstallation of SF

.................................................. 158

Chapter 19 Uninstalling Storage Foundation

................................... 159

Removing VxFS file systems ......................................................... 159

Removing rootability .................................................................... 160

Moving volumes to disk partitions ................................................... 161

Moving volumes onto disk partitions using VxVM ......................... 161

Removing the Replicated Data Set ................................................. 163

Contents 12

Chapter 20

Uninstalling SF RPMs using the script-based installer ........................ 165

Uninstalling SF with the web-based installer ..................................... 166

Removing license files (Optional) ................................................... 167

Removing the Storage Foundation for Databases (SFDB) repository ............................................................................ 167

Uninstalling SF using response files

............................. 169

Uninstalling SF using response files ............................................... 169

Response file variables to uninstall Storage Foundation ...................... 170

Sample response file for SF uninstallation ........................................ 170

Section 7 Installation reference

.............................................. 172

Appendix A

Appendix B

Appendix C

Installation scripts

............................................................ 173

Installation script options .............................................................. 173

Tunable files for installation

........................................... 179

About setting tunable parameters using the installer or a response file ..................................................................................... 179

Setting tunables for an installation, configuration, or upgrade ............... 180

Setting tunables with no other installer-related operations ................... 181

Setting tunables with an un-integrated response file ........................... 182

Preparing the tunables file ............................................................ 183

Setting parameters for the tunables file ........................................... 183

Tunables value parameter definitions .............................................. 184

Configuring the secure shell or the remote shell for communications

.......................................................... 192

About configuring secure shell or remote shell communication modes before installing products ........................................................ 192

Manually configuring passwordless ssh ........................................... 193

Setting up ssh and rsh connection using the installer -comsetup command ............................................................................ 197

Setting up ssh and rsh connection using the pwdutil.pl utility ................ 198

Restarting the ssh session ............................................................ 201

Enabling rsh for Linux .................................................................. 201

Contents 13

Appendix D

Appendix E

Storage Foundation components

................................... 204

Storage Foundation installation RPMs ............................................. 204

Symantec Storage Foundation obsolete and reorganized installation

RPMs ................................................................................. 207

Troubleshooting installation issues

.............................. 210

Restarting the installer after a failed connection ................................ 210

What to do if you see a licensing reminder ....................................... 210

About the VRTSspt RPM troubleshooting tools ................................. 211

Incorrect permissions for root on remote system ............................... 212

Inaccessible system .................................................................... 213

Upgrading Symantec Storage Foundation for Databases (SFDB) tools from 5.0.x to 6.2 (2184482) ..................................................... 213

Troubleshooting the webinstaller .................................................... 213

Appendix F Compatability issues when installing Storage

Foundation with other products

.............................. 215

Installing, uninstalling, or upgrading Storage Foundation products when other Symantec products are present ........................................ 215

Installing, uninstalling, or upgrading Storage Foundation products when

VOM is already present .......................................................... 216

Installing, uninstalling, or upgrading Storage Foundation products when

NetBackup is already present .................................................. 216

Index

................................................................................................................... 217

Section

1

Installation overview and planning

Chapter 1. Introducing Storage Foundation

Chapter 2. System requirements

Chapter 3. Planning to install Storage Foundation

Chapter 4. Licensing Storage Foundation

Chapter

1

Introducing Storage

Foundation

This chapter includes the following topics:

About Storage Foundation

About Veritas Operations Manager

About Symantec Operations Readiness Tools

About Storage Foundation

Symantec Storage Foundation includes Veritas File System by Symantec (VxFS) and Veritas Volume Manager by Symantec (VxVM) with various feature levels.

Veritas File System is a high-performance journaling file system that provides easy management and quick-recovery for applications. Veritas File System delivers scalable performance, continuous availability, increased I/O throughput, and structural integrity.

Veritas Volume Manager removes the physical limitations of disk storage. You can configure, share, manage, and optimize storage I/O performance online without interrupting data availability. Veritas Volume Manager also provides easy-to-use, online storage management tools to reduce downtime.

VxFS and VxVM are a part of all Symantec Storage Foundation products. Do not install or update VxFS or VxVM as individual components.

Storage Foundation Basic supports all Storage Foundation Standard features, however, there are deployment and technical support limitations.

Introducing Storage Foundation

About Veritas Operations Manager

16

About Symantec Replicator Option

Symantec Replicator Option is an optional, separately-licensable feature.

File Replicator enables replication at the file level over IP networks. File Replicator leverages data duplication, provided by Veritas File System, to reduce the impact of replication on network resources.

Volume Replicator replicates data to remote locations over any standard IP network to provide continuous data availability and disaster recovery.

Volume Replicator is available with Storage Foundation, Storage Foundation High

Availability, Storage Foundation Cluster File System, Storage Foundation for Oracle

RAC, and Storage Foundation for SybaseCE.

Before installing this option, read the Release Notes for the product.

To install the option, follow the instructions in the Installation Guide for the product.

About Veritas Operations Manager

Veritas Operations Manager provides a centralized management console for

Symantec Storage Foundation and High Availability products. You can use Veritas

Operations Manager to monitor, visualize, and manage storage resources and generate reports.

Symantec recommends using Veritas Operations Manager (VOM) to manage

Storage Foundation and Cluster Server environments.

You can download Veritas Operations Manager from http://go.symantec.com/vom .

Refer to the Veritas Operations Manager documentation for installation, upgrade, and configuration instructions.

The Veritas Enterprise Administrator (VEA) console is no longer packaged with

Storage Foundation products. If you want to continue using VEA, a software version is available for download from http://www.symantec.com/operations-manager/support . Symantec Storage

Foundation Management Server is deprecated.

About Symantec Operations Readiness Tools

Symantec Operations Readiness Tools (SORT) is a website that automates and simplifies some of the most time-consuming administrative tasks. It helps you identify risks in your datacenters and improve operational efficiency, enabling you to manage the complexity that is associated with datacenter architectures and scale.

Introducing Storage Foundation

About Symantec Operations Readiness Tools

17

Table 1-1

lists three major datacenter tasks and the SORT tools that can help you accomplish them.

Table 1-1 Datacenter tasks and the SORT tools

Task

Prepare for installations and upgrades

Identify risks and get server-specific recommendations

SORT tools

Installation and Upgrade checklists

Display system requirements including memory, disk space, and architecture.

Installation and Upgrade custom reports

Create reports that determine if you're ready to install or upgrade a Symantec enterprise product.

Array-specific Module Finder

List the latest Array Support Libraries (ASLs) and Array

Policy Modules (APMs) for UNIX servers, and Device

Driver Installers (DDIs) and Device Discovery Layers

(DDLs) for Windows servers.

High Availability Agents table

Find and download the agents for applications, databases, replication, and Symantec partners.

Patch notifications

Receive automatic email notifications about patch updates. (Sign in required.)

Risk Assessment check lists

Display configuration recommendations based on your

Symantec product and platform.

Risk Assessment custom reports

Create reports that analyze your system and give you recommendations about system availability, storage use, performance, and best practices.

Error code descriptions and solutions

Display detailed information on thousands of Symantec error codes.

Introducing Storage Foundation

About Symantec Operations Readiness Tools

18

Table 1-1

Task

Improve efficiency

Datacenter tasks and the SORT tools (continued)

SORT tools

Patch Finder

List and download patches for your Symantec enterprise products.

License/Deployment custom reports

Create custom reports that list your installed Symantec products and license keys. Display licenses by product, platform, server tier, and system.

Symantec Performance Value Unit (SPVU) Calculator

Use the calculator to assist you with the pricing meter transition.

Documentation

List and download Symantec product documentation, including manual pages, product guides, and support articles.

Related links

Display links to Symantec product support, forums, customer care, and vendor information on a single page.

SORT is available at no additional charge.

To access SORT, go to: https://sort.symantec.com

Chapter

2

System requirements

This chapter includes the following topics:

Release notes

Important preinstallation information for SF

Supported operating systems

Storage Foundation memory requirements

Disk space requirements

Checking installed product versions and downloading maintenance releases and patches

Obtaining installer patches

Disabling external network connection attempts

Database requirements

VxVM licenses

Cross-Platform Data Sharing licensing

Release notes

The Release Notes for each Symantec product contains last-minute news and important details for each product, including updates to system requirements and supported software. Review the Release notes for the latest information before you start installing the product.

The product documentation is available on the web at the following location: https://sort.symantec.com/documents

System requirements

Important preinstallation information for SF

20

Important preinstallation information for SF

Before you install SF, make sure that you have reviewed the following information:

■ Preinstallation checklist for your configuration. Go to the SORT installation checklist tool . From the drop-down lists, select the information for the Symantec product you want to install, and click Generate Checklist.

Hardware compatibility list for information about supported hardware: http://www.symantec.com/docs/TECH211575

For important updates regarding this release, review the Late-Breaking News

Technote on the Symantec Technical Support website: http://www.symantec.com/docs/TECH211540

Supported operating systems

For information on supported operating systems for various components of SF, see the Storage Foundation Release Notes.

Storage Foundation memory requirements

A minimum of 1 GB of memory is strongly recommended.

Disk space requirements

Before installing your products, confirm that your system has enough free disk space.

Use the Perform a Preinstallation Check (P) menu for the web-based installer to determine whether there is sufficient space.

Or, go to the installation directory and run the installer with the -precheck option.

# ./installer -precheck

See

“About the script-based installer”

on page 41.

Checking installed product versions and downloading maintenance releases and patches

Symantec provides a means to check the Symantec RPMs you have installed, and download any needed maintenance releases and patches.

System requirements

Checking installed product versions and downloading maintenance releases and patches

21

Use the installer command with the

-version option to determine what is installed on your system, and download any needed maintenance releases or patches. After you have installed the current version of the product, you can use the showversion script in the

/opt/VRTS/install directory to find product information.

The version option or the showversion script checks the specified systems and discovers the following:

SF product versions that are installed on the system

All the required RPMs and the optional Symantec RPMs installed on the system

Any required or optional RPMs (if applicable) that are not present

Installed patches

Available base releases (major or minor)

Available maintenance releases

Available patch releases

To check your systems and download maintenance releases and patches

1 Mount the media, or navigate to the installation directory.

2 Start the installer with the

-version option.

# ./installer -version sys1 sys2

For each system, the installer lists all of the installed base releases, maintenance releases, and patches, followed by the lists of available downloads.

3 If you have Internet access, follow the prompts to download the available maintenance releases and patches to the local system.

4 If you do not have Internet access, you can download any needed maintenance releases and patches from the Symantec Operations Readiness Tools (SORT)

Patch Finder page at: https://sort.symantec.com/patch/finder

You can obtain installer patches automatically or manually.

See

“Obtaining installer patches”

on page 22.

Downloading maintenance releases and patches requires the installer to make outbound networking calls. You can also disable external network connection attempts.

See

“Disabling external network connection attempts”

on page 23.

System requirements

Obtaining installer patches

22

Obtaining installer patches

Symantec occasionally finds issues with the Storage Foundation installer, and posts public installer patches on the Symantec Operations Readiness Tools (SORT) website's Patch Finder page at: https://sort.symantec.com/patch/finder

You can access installer patches automatically or manually.

To download installer patches automatically

◆ Starting with Storage Foundation version 6.1, installer patches are downloaded automatically. No action is needed on your part.

If you are running Storage Foundation version 6.1 or later, and your system has Internet access, the installer automatically imports any needed installer patch, and begins using it.

Automatically downloading installer patches requires the installer to make outbound networking calls. You can also disable external network connection attempts.

See

“Disabling external network connection attempts”

on page 23.

If your system does not have Internet access, you can download installer patches manually.

To download installer patches manually

1 Go to the Symantec Operations Readiness Tools (SORT) website's Patch

Finder page, and save the most current Symantec patch on your local system.

2 Navigate to the directory where you want to unzip the file you downloaded in step

1

.

3 Unzip the patch tar file. For example, run the following command:

# gunzip cpi-6.2P2-patches.tar.gz

4 Untar the file. For example, enter the following:

# tar -xvf cpi-6.2P2-patches.tar patches/ patches/CPI62P2.pl

README

System requirements

Disabling external network connection attempts

23

5 Navigate to the installation media or to the installation directory.

6 To start using the patch, run the installer command with the -require option.

For example, enter the following:

# ./installer -require /target_directory/patches/CPI62P2.pl

Disabling external network connection attempts

When you execute the installer command, the installer attempts to make an outbound networking call to get information about release updates and installer patches. If you know your systems are behind a firewall, or do not want the installer to make outbound networking calls, you can disable external network connection attempts by the installer.

To disable external network connection attempts

◆ Disable inter-process communication (IPC).

To disable IPC, run the installer with the

-noipc option.

For example, to disable IPC for system1 (sys1) and system2 (sys2) enter the following:

# ./installer -noipc sys1 sys2

Database requirements

The following TechNote identifies the most current information on supported database and operating system combinations: http://www.symantec.com/docs/DOC4039

Note: SF supports running Oracle and Sybase on VxFS and VxVM.

SF does not support running SFDB tools with Sybase.

VxVM licenses

The following table shows the levels of licensing in Veritas Volume Manager and the features supported at each level.

Table 2-1

describes the levels of licensing in Veritas Volume Manager and supported features.

System requirements

Cross-Platform Data Sharing licensing

24

Table 2-1 Levels of licensing in Veritas Volume Manager and supported features

VxVM License

Full

Add-on Licenses

Description of Supported Features

Concatenation, spanning, rootability, volume resizing, multiple disk groups, co-existence with native volume manager, striping, mirroring,

DRL logging for mirrors, striping plus mirroring, mirroring plus striping,

RAID-5, RAID-5 logging, Smartsync, hot sparing, hot-relocation, online data migration, online relayout, volume snapshots, volume sets,

Intelligent Storage Provisioning, FastResync with Instant Snapshots,

Storage Expert, Device Discovery Layer (DDL), Dynamic Multi-Pathing

(DMP), and Veritas Operations Manager (VOM).

Features that augment the Full VxVM license such as clustering functionality (cluster-shareable disk groups and shared volumes) and

Symantec Volume Replicator.

Note: You need a Full VxVM license to make effective use of add-on licenses to

VxVM.

To see the license features that are enabled in VxVM

◆ Enter the following command:

# vxdctl license

Cross-Platform Data Sharing licensing

The Cross-Platform Data Sharing (CDS) feature is also referred to as Portable Data

Containers.

The ability to import a CDS disk group on a platform that is different from the platform on which the disk group was last imported is controlled by a CDS license. CDS licenses are included as part of the Symantec Storage Foundation license.

Chapter

3

Planning to install Storage

Foundation

This chapter includes the following topics:

About planning for SF installation

About installation and configuration methods

Downloading the Storage Foundation software

About planning for SF installation

Before you continue, make sure that you have the current version of this guide.

The latest documentation is available on the Symantec Operations Readiness Tools

(SORT) website.

https://sort.symantec.com/documents

Document version: 6.2 Rev 2.

This installation guide is designed for system administrators who already have basic knowledge of UNIX system and network administration. Basic knowledge includes commands such as tar

, mkdir

, and simple shell scripting. What is also required is familiarity with the specific platform and operating system where SF is to be installed.

Follow the preinstallation instructions if you want to install Storage Foundation.

The following Symantec Storage Foundation products are installed with these instructions:

Symantec Storage Foundation Basic

■ Symantec Storage Foundation (Standard and Enterprise Editions)

Planning to install Storage Foundation

About installation and configuration methods

26

Several component products are bundled with each of these SF products.

About installation and configuration methods

You can install and configure SF using Symantec installation programs or using native operating system methods.

Table 3-1

shows the installation and configuration methods that SF supports.

Table 3-1 Installation and configuration methods

Method

The script-based installer

The web-based installer

Description

Using the script-based installer, you can install Symantec products from a driver system running a supported platform to target computers running any supported platform.

To install your Symantec product using the installer, choose one of the following:

■ The general product installer: installer

The general product installer script provides a menu that simplifies the selection of installation and configuration options. Use the general product installer if you want to install multiple products from a disc.

■ Product-specific installation scripts: installsf<version>

The product-specific installation scripts provide command-line interface options. Installing and configuring with the installsf script is identical to running the general product installer and specifying SF from the list of products to install.

Use the product-specific installation scripts to install or configure individual products you download electronically.

See

“About the script-based installer”

on page 41.

Using the web-based installer, you can install Symantec products from a driver system running a supported platform to target computers running any supported platform

The web-based installer provides an interface to manage the installation and configuration from a remote site using a standard web browser.

webinstaller

See

“About the web-based installer”

on page 47.

Planning to install Storage Foundation

About installation and configuration methods

27

Table 3-1

Method

Deployment Server

Installation and configuration methods (continued)

Description

Using the Deployment Server, you can store multiple release images in one central location and deploy them to systems of any supported platform.

See

“About the Deployment Server”

on page 77.

Silent installation using response files

Response files automate installation and configuration by using the information that is stored in a specified file instead of prompting you for information.

You can use any of the above options to generate a response file. You can then customize the response file for another system. Run the product installation script with the response file option to install silently on one or more systems.

See

“About response files”

on page 27.

Install Bundles Beginning with version 6.1, you can easily install or upgrade your systems directly to a base, maintenance, or patch level in one step using Install Bundles.

The installer installs both releases as if they were combined in the same release image. The various scripts, RPMs, and patch components are merged, and multiple releases are installed together as if they are one combined release.

See

“Using Install Bundles to simultaneously install or upgrade full releases (base, maintenance, rolling patch), and individual patches”

on page 120.

Kickstart

(For RedHat Linux systems)

Kickstart lets you automatically install systems based on predefined customized configurations.

See

“Installing SF using Kickstart”

on page 61.

yum

(For RedHat Linux systems)

You can install SFRPMs into the yum repository. yum is supported for Red Hat Enterprise Linux 6 and Red Hat

Enterprise Linux 7.

About response files

The installer script or product installation script generates a response file during any installation, configuration, upgrade, or uninstall procedure. The response file contains the configuration information that you entered during the procedure. When the procedure completes, the installation script displays the location of the response files.

Planning to install Storage Foundation

Downloading the Storage Foundation software

28

You can use the response file for future installation procedures by invoking an installation script with the

-responsefile option. The response file passes arguments to the script to automate the installation of that product. You can edit the file to automate installation and configuration of additional systems.

You can generate a response file using the -makeresponsefile option.

See

“Installation script options”

on page 173.

Syntax in the response file

The syntax of the Perl statements that is included in the response file variables varies. It can depend on whether the variables require scalar or list values.

For example, in the case of a string value:

$CFG{Scalar_variable}="value"; or, in the case of an integer value:

$CFG{Scalar_variable}=123; or, in the case of a list:

$CFG{List_variable}=["value 1 ", "value 2 ", "value 3 "];

Downloading the Storage Foundation software

One method of obtaining the Storage Foundation software is to download it to your local system from the Symantec website.

For a Trialware download, perform the following. Contact your Symantec representative for more information.

To download the trialware version of the software

1 Open the following link in your browser: http://www.symantec.com/index.jsp

2 In Products and Solutions section, click the Trialware link.

3 On the next page near the bottom of the page, click Business Continuity.

4 Under Cluster Server, click Download.

5 In the new window, click Download Now.

6 Review the terms and conditions, and click I agree.

Planning to install Storage Foundation

Downloading the Storage Foundation software

29

7 You can use existing credentials to log in or create new credentials.

8 Find the product that you want to download and select it. Continue with the installation.

If you download a standalone Symantec product, the single product download files do not contain the product installer. Use the installation script for the specific product to install the product.

Note: Trialware is the full product version. The enabled licensing places the product in a demo or a trial state.

See

“About the script-based installer”

on page 41.

To download the software

1 Verify that you have enough space on your filesystem to store the downloaded software.

The estimated space for download, gunzip, and tar extract is 1 GB.

If you plan to install the software on the same system, make sure that you also have enough space for the installed software.

See

“Disk space requirements”

on page 20.

2 To see the space available, you can use the df command with the name of the local file system where you intend to download the software.

# df -k filesystem

Caution: When you select a location to download files, do not select a directory that contains Symantec products from a previous release or maintenance pack.

Make sure that different versions exist in different directories.

3 Download the software, specifying the file system with sufficient space for the file.

Chapter

4

Licensing Storage

Foundation

This chapter includes the following topics:

About Symantec product licensing

Setting or changing the product level for keyless licensing

Installing Symantec product license keys

About Symantec product licensing

You have the option to install Symantec products without a license key. Installation without a license does not eliminate the need to obtain a license. A software license is a legal instrument governing the usage or redistribution of copyright protected software. The administrator and company representatives must ensure that a server or cluster is entitled to the license level for the products installed. Symantec reserves the right to ensure entitlement and compliance through auditing.

If you encounter problems while licensing this product, visit the Symantec licensing

Support website.

http://www.symantec.com/products-solutions/licensing/activating-software/ detail.jsp?detail_id=licensing_portal

The product installer prompts you to select one of the following licensing methods:

Install a license key for the product and features that you want to install.

When you purchase a Symantec product, you receive a License Key certificate.

The certificate specifies the product keys and the number of product licenses purchased.

Continue to install without a license key.

Licensing Storage Foundation

Setting or changing the product level for keyless licensing

31

The installer prompts for the product modes and options that you want to install, and then sets the required product level.

Within 60 days of choosing this option, you must install a valid license key corresponding to the license level entitled, or continue with keyless licensing by managing the systems with a management server. If you do not comply with the above terms, continuing to use the Symantec product is a violation of your

End User License Agreement, and results in warning messages

For more information about keyless licensing, see the following URL: http://go.symantec.com/sfhakeyless

If you upgrade to this release from a previous release of the Symantec software, the installer asks whether you want to upgrade the key to the new version. The existing license keys may not activate new features in this release.

If you upgrade with the product installer, or if you install or upgrade with a method other than the product installer, you must do one of the following to license the products:

■ Run the vxkeyless command to set the product level for the products you have purchased. This option also requires that you manage the server or cluster with a management server.

See

“Setting or changing the product level for keyless licensing”

on page 31.

See the vxkeyless(1m) manual page.

■ Use the vxlicinst command to install a valid product license key for the products you have purchased.

See

“Installing Symantec product license keys”

on page 33.

See the vxlicinst(1m) manual page.

You can also use the above options to change the product levels to another level that you are authorized to use. For example, you can add the replication option to the installed product. You must ensure that you have the appropriate license for the product level and options in use.

Note: To change from one product group to another, you may need to perform additional steps.

Setting or changing the product level for keyless licensing

The keyless licensing method uses product levels to determine the Symantec products and functionality that are licensed.

Licensing Storage Foundation

Setting or changing the product level for keyless licensing

32

For more information to use keyless licensing and to download the management server, see the following URL: http://go.symantec.com/vom

When you set the product license level for the first time, you enable keyless licensing for that system. If you install with the product installer and select the keyless option, you are prompted to select the product and feature level that you want to license.

When you upgrade from a previous release, the product installer prompts you to update the vxkeyless license product level to the current release level. If you update the vxkeyless license product level during the upgrade process, no further action is required. If you do not update the vxkeyless license product level, the output you see when you run the vxkeyless display command includes the previous release's vxkeyless license product level. Each vxkeyless license product level name includes the suffix _previous_release_version. For example, DMP_6.0, or

SFENT_VR_5.1SP1, or VCS_GCO_5.1. If there is no suffix, it is the current release version.

You would see the suffix _previous_release_version if you did not update the vxkeyless product level when prompted by the product installer. Symantec highly recommends that you always use the current release version of the product levels.

To do so, use the vxkeyless set command with the desired product levels. If you see SFENT_60, VCS_60, use the vxkeyless set SFENT,VCS command to update the product levels to the current release.

After you install or upgrade, you can change product license levels at any time to reflect the products and functionality that you want to license. When you set a product level, you agree that you have the license for that functionality.

To set or change the product level

1 Change your current working directory:

# export PATH=$PATH:/opt/VRTSvlic/bin

2 View the current setting for the product level.

# vxkeyless -v display

Licensing Storage Foundation

Installing Symantec product license keys

33

3 View the possible settings for the product level.

# vxkeyless displayall

4 Set the desired product level.

# vxkeyless set prod_levels where prod_levels is a comma-separated list of keywords. The keywords are the product levels as shown by the output of step

3

.

If you want to remove keyless licensing and enter a key, you must clear the keyless licenses. Use the NONE keyword to clear all keys from the system.

Warning: Clearing the keys disables the Symantec products until you install a new key or set a new product level.

See

“Installing Symantec product license keys”

on page 33.

To clear the product license level

1 View the current setting for the product license level.

# vxkeyless [-v] display

2 If there are keyless licenses installed, remove all keyless licenses:

# vxkeyless [-q] set NONE

For more details on using the vxkeyless utility, see the vxkeyless(1m) manual page.

Installing Symantec product license keys

The VRTSvlic RPM enables product licensing. After the VRTSvlic is installed, the following commands and their manual pages are available on the system: vxlicinst vxlicrep vxlictest

Installs a license key for a Symantec product

Displays the currently installed licenses

Retrieves the features and their descriptions that are encoded in a license key

Even though other products are included on the enclosed software discs, you can only use the Symantec software products for which you have purchased a license.

Licensing Storage Foundation

Installing Symantec product license keys

34

To install or change a license

1 Run the following commands. In a cluster environment, run the commands on each node in the cluster:

# cd /opt/VRTS/bin

# ./vxlicinst -k license key

2 Run the following Veritas Volume Manager (VxVM) command to recognize the new license:

# vxdctl license init

See the vxdctl(1M) manual page.

If you have vxkeyless licensing, you can view or update the keyless product licensing levels.

See

“Setting or changing the product level for keyless licensing”

on page 31.

Section

2

Installation of Storage

Foundation

Chapter 5. Preparing to install Storage Foundation

Chapter 6. Installing Storage Foundation using the script-based installer

Chapter 7. Installing Storage Foundation using the web-based installer

Chapter 8. Automated installation using response files

Chapter 9. Installing Storage Foundation using operating system-specific methods

Chapter 10. Configuring Storage Foundation

Chapter

5

Preparing to install Storage

Foundation

This chapter includes the following topics:

Installation preparation overview

About using ssh or rsh with the installer

Setting environment variables

Mounting the product disc

Assessing the system for installation readiness

Installation preparation overview

Table 5-1

provides an overview of an installation using the product installer.

Table 5-1 Installation overview

Installation task Section

Obtain product licenses.

See

“About Symantec product licensing”

on page 30.

Download the software, or insert the product

DVD.

See

“Downloading the Storage Foundation software”

on page 28.

See

“Mounting the product disc”

on page 38.

Set environment variables.

See

“Setting environment variables”

on page 37.

Preparing to install Storage Foundation

About using ssh or rsh with the installer

37

Table 5-1 Installation overview (continued)

Installation task Section

Configure the Secure Shell (ssh) or Remote

Shell (rsh) on all nodes.

See

“About configuring secure shell or remote shell communication modes before installing products”

on page 192.

Verify that hardware, software, and operating system requirements are met.

See

“Release notes”

on page 19.

Check that sufficient disk space is available.

See

“Disk space requirements”

on page 20.

Use the installer to install the products.

See

“About the script-based installer”

on page 41.

About using ssh or rsh with the installer

The installer uses passwordless Secure Shell (ssh) or Remote Shell (rsh) communications among systems. The installer uses the ssh daemon or rsh daemon that comes bundled with the operating system. During an installation, you choose the communication method that you want to use. Or, you can run the installer

-comsetup command to set up ssh or rsh explicitly. You then provide the installer with the superuser passwords for the systems where you plan to install. When the installation process completes, the installer asks you if you want to remove the password-less connection. If installation terminated abruptly, use the installation script's

-comcleanup option to remove the ssh configuration or rsh configuration from the systems.

See

“Installation script options”

on page 173.

In most installation, configuration, upgrade (where necessary), and uninstallation scenarios, the installer can configure ssh or rsh on the target systems. In the following scenarios, you need to set up ssh or rsh manually, or use the installer

-comsetup option to set up an ssh or rsh configuration from the systems.

When you perform installer sessions using a response file.

See

“About configuring secure shell or remote shell communication modes before installing products”

on page 192.

Setting environment variables

Most of the commands which are used in the installation are present in the

/sbin or

/usr/sbin directory. Add these directories to your

PATH environment variable as necessary.

Preparing to install Storage Foundation

Mounting the product disc

38

After installation, SF commands are in

/opt/VRTS/bin

. SF manual pages are stored in

/opt/VRTS/man

.

Specify /opt/VRTS/bin in your PATH after the path to the standard Linux commands.

Some VCS custom scripts reside in /opt/VRTSvcs/bin . If you want to install a high availability product, add /opt/VRTSvcs/bin to the PATH also.

To invoke the VxFS-specific df

, fsdb

, ncheck

, or umount commands, type the full path name:

/opt/VRTS/bin/command

.

To set your

MANPATH environment variable to include

/opt/VRTS/man do the following:

■ If you want to use a shell such as sh or bash , enter the following:

$ MANPATH=$MANPATH:/opt/VRTS/man; export MANPATH

■ If you want to use a shell such as csh or tcsh , enter the following:

% setenv MANPATH $(MANPATH):/opt/VRTS/man

On a Red Hat system, also include the 1m manual page section in the list defined by your

MANSECT environment variable.

■ If you want to use a shell such as sh or bash , enter the following:

$ MANSECT=$MANSECT:1m; export MANSECT

■ If you want to use a shell such as csh or tcsh , enter the following:

% setenv MANSECT $(MANSECT):1m

If you use the man (1) command to access manual pages, set LC_ALL=C in your shell to ensure that they display correctly.

Mounting the product disc

You must have superuser (root) privileges to load the SF software.

Preparing to install Storage Foundation

Assessing the system for installation readiness

39

To mount the product disc

1 Log in as superuser on a system where you want to install SF.

The systems must be in the same subnet.

2 Insert the product disc with the SF software into a drive that is connected to the system.

The disc is automatically mounted.

3 If the disc does not automatically mount, then enter:

# mount -t iso9660 /dev/sr0 /media

4 Navigate to the location of the RPMs.

# cd /mnt/cdrom/dist_arch/rpms

Where dist is rhel6, rhel7 or sles11, and arch is x86_64 for RHEL and SLES.

Assessing the system for installation readiness

Symantec provides the following tools for assessing your system, to ensure that the system meets the requirements for installing Symantec Storage Foundation

6.2.

Symantec Operations Readiness Tools Symantec Operations Readiness Tools

(SORT) is a web-based application that is designed to support Symantec enterprise products.

See

“About Symantec Operations Readiness

Tools”

on page 16.

Prechecking your systems using the installer Performs a preinstallation check on the specified systems. The product installer reports whether the specified systems meet the minimum requirements for installing

Symantec Storage Foundation 6.2.

See

“Prechecking your systems using the installer”

on page 39.

Prechecking your systems using the installer

The script-based and web-based installer's precheck option checks for the following:

■ Recommended swap space for installation

Preparing to install Storage Foundation

Assessing the system for installation readiness

40

■ Recommended memory sizes on target systems for Symantec programs for best performance

■ Required operating system versions

To use the precheck option

1 Start the script-based or web-based installer.

See

“Installing Storage Foundation using the script-based installer”

on page 43.

See

“Installing SF with the web-based installer”

on page 50.

2 Select the precheck option:

From the web-based installer, select the Perform a Pre-Installation Check from the Task pull-down menu.

■ In the script-based installer, from root on the system where you want to perform the check, start the installer.

# ./installer

In the Task Menu, press the p key to start the precheck.

3 Enter the system name or the IP address of the system that you want to check.

4 Review the output and make the changes that the installer recommends.

Chapter

6

Installing Storage

Foundation using the script-based installer

This chapter includes the following topics:

About the script-based installer

Installing Storage Foundation using the script-based installer

About the script-based installer

You can use the script-based installer to install Symantec products (version 6.1

and later) from a driver system that runs any supported platform to a target system that runs different supported platforms.

To install your Symantec product, use one of the following methods:

The general product installer ( installer

). The general product installer script provides a menu that simplifies the selection of installation and configuration options. Use the general product installer if you want to install multiple products from a disc.

See

“Installing Storage Foundation using the script-based installer”

on page 43.

Product-specific installation scripts ( installsf

). The product-specific installation scripts provide command-line interface options. Installing and configuring with the installsf script is identical to running the general product installer and specifying SF from the list of products to install. Use the product-specific installation scripts to install or configure individual products you download electronically. You can find these scripts at the root of the product media. These scripts are also installed with the product.

Installing Storage Foundation using the script-based installer

About the script-based installer

42

Table 6-1

lists all the SFHA Solutions product installation scripts. The list of product-specific installation scripts that you find on your system depends on the product that you install on your system.

Table 6-1 Product installation scripts

Symantec product name

Script name in the media

For all SFHA Solutions products installer

Symantec ApplicationHA installapplicationha

Symantec Cluster

Server (VCS)

Symantec Storage

Foundation (SF) installvcs installsf

Symantec Storage

Foundation and High

Availability (SFHA) installsfha

Symantec Storage

Foundation Cluster File

System High Availability

(SFCFSHA) installsfcfsha

Symantec Storage

Foundation for Oracle

RAC (SF Oracle RAC) installsfrac

Symantec Dynamic

Multi-pathing (DMP) installdmp

Script name after an installation

N/A installapplicationha<version> installvcs<version> installsf<version> installsfha<version> installsfcfsha<version> installsfrac<version> installdmp<version>

When you install from the installation media, the script name does not include a product version.

When you configure the product after an installation, the installation scripts include the product version in the script name.

For example, for the 6.2 version:

# /opt/VRTS/install<productname>62 -configure

Note: The general product installer ( installer ) script does not include the product version.

Installing Storage Foundation using the script-based installer

Installing Storage Foundation using the script-based installer

43

At most points during the installation you can type the following characters for different actions:

Use b (back) to return to a previous section of the installation procedure. The back feature of the installation scripts is context-sensitive, so it returns to the beginning of a grouped section of questions.

Use

Ctrl+c to stop and exit the program if an installation procedure hangs.

After a short delay, the script exits.

Use q to quit the installer.

Use ?

to display help information.

Use the Enter button to accept a default response.

See

“Installation script options”

on page 173.

Installing Storage Foundation using the script-based installer

The product installer is the recommended method to license and install Storage

Foundation.

The following sample procedure is based on the installation of Storage Foundation on a single system.

To install Storage Foundation

1 Set up the systems so that the commands execute on remote machines without prompting for passwords or confirmations with remote shell or secure shell communication utilities.

See

“About configuring secure shell or remote shell communication modes before installing products”

on page 192.

2 Load and mount the software disc. If you downloaded the software, navigate to the top level of the download directory and skip the next step.

See

“Mounting the product disc”

on page 38.

3 Move to the top-level directory on the disc.

# cd /mnt/cdrom/dist_arch

Where dist is rhel6, rhel7 or sles11, and arch is x86_64 for RHEL and SLES.

Installing Storage Foundation using the script-based installer

Installing Storage Foundation using the script-based installer

44

4 From this directory, type the following command to start the installation on the local system. Use this command to install on remote systems if secure shell or remote shell communication modes are configured:

# ./installer

5 Press

I to install and press Enter.

6 When the list of available products is displayed, select Storage Foundation, enter the corresponding number, and press Enter.

7 At the prompt, specify whether you accept the terms of the End User License

Agreement (EULA).

Do you agree with the terms of the End User License Agreement as specified in the storage_foundation/EULA/lang/

EULA_SFHA_Ux_version.pdf file present on the media? [y,n,q,?] y

8 Select from one of the following installation options:

Minimal RPMs: installs only the basic functionality for the selected product.

Recommended RPMs: installs the full feature set without optional RPMs.

■ All RPMs: installs all available RPMs.

Each option displays the disk space that is required for installation. Select which option you want to install and press Enter.

9 You are prompted to enter the system names where you want to install the software. Enter the system name or names and then press Enter.

Enter the system names separated by spaces:

[q,?] sys1 sys2

10 After the system checks complete, the installer displays a list of the RPMs to be installed. Press Enter to continue with the installation.

11 If the coomunication fails during the precheck, the installer can configure remote shell or secure shell communications for you among systems, however each system needs to have rsh or ssh servers installed. You also need to provide the superuser passwords for the systems. Note that for security reasons, the installation program neither stores nor caches these passwords.

12 The installer may prompt to restore previous Veritas Volume Manager configurations.

Installing Storage Foundation using the script-based installer

Installing Storage Foundation using the script-based installer

45

13 Choose the licensing method. Answer the licensing questions and follow the prompts.

Note: The keyless license option enables you to install without entering a key.

However, you still need a valid license to install and use Symantec products.

Keyless licensing requires that you manage the systems with a Management

Server.

See

“About Symantec product licensing”

on page 30.

14 You are prompted to enter the Standard or Enterprise product mode.

1) SF Standard

2) SF Enterprise b) Back to previous menu

Select product mode to license: [1-2,b,q,?] (2) 1

15 If you selects product licensing mode as 2 ( SF Enterprise), the installer prompts you to decide to enable replication or not:

Would you like to enable the Volume Replicator?

[y,n,q] (n)

Enter your option.

16 If Veritas Volume Manager (VxVM) is started and the installer detects the presence of a Solid State Drive (SSD) device, the installer displays the following message:

SSD devices have been detected on systemname.

It is strongly recommended that you use the SmartIO feature to accelerate I/O performance.

See the Storage Foundation and

High Availability Solutions documentation for more information on using the SmartIO feature.

Installing Storage Foundation using the script-based installer

Installing Storage Foundation using the script-based installer

46

17 At the prompt, specify whether you want to send your installation information to Symantec.

Installation procedures and diagnostic information were saved in the log files under directory /var/tmp/installer-<platform>-<uuid>.

Analyzing this information helps Symantec discover and fix failed operations performed by the installer.

Would you like to send the information about this installation to

Symantec to help improve installation in the future? [y,n,q,?] (y) y

18 Check the log file, if needed, to confirm the installation and configuration.

Chapter

7

Installing Storage

Foundation using the web-based installer

This chapter includes the following topics:

About the web-based installer

Before using the web-based installer

Starting the web-based installer

Obtaining a security exception on Mozilla Firefox

Performing a preinstallation check with the web-based installer

Installing SF with the web-based installer

About the web-based installer

Use the web-based installer interface to install Symantec products. The web-based installer can perform most of the tasks that the script-based installer performs.

You use the webinstaller script to start and stop the Veritas XPortal Server xprtlwid process. The webinstaller script can also be used to check the status of the XPortal Server.

When the webinstaller script starts the xprtlwid process, the script displays a

URL. Use this URL to access the web-based installer from a web browser such as

Internet Explorer or FireFox.

The web installer creates log files whenever the web installer operates. While the installation processes operate, the log files are located in a session-based directory

Installing Storage Foundation using the web-based installer

Before using the web-based installer

48 under the

/var/tmp directory. After the install process completes, the log files are located in the

/opt/VRTS/install/logs directory. Symantec recommends that you keep these files for auditing, debugging, and future use.

The location of the Veritas XPortal Server configuration file is

/var/opt/webinstaller/xprtlwid.conf

.

See

“Before using the web-based installer”

on page 48.

See

“Starting the web-based installer”

on page 48.

Before using the web-based installer

The web-based installer requires the following configuration.

Table 7-1 Web-based installer requirements

System

Target system

Function Requirements

The systems where you plan to install the Symantec products.

Must be a supported platform for Symantec

Storage Foundation 6.2.

Installation server

Administrative system

The server where you start the installation. The installation media is accessible from the installation server.

Must be at one of the supported operating system update levels.

The system where you run the web browser to perform the installation.

Must have a web browser.

Supported browsers:

Internet Explorer 6, 7, and 8

Firefox 3.x and later

Starting the web-based installer

This section describes starting the web-based installer.

To start the web-based installer

1 Mount the installation media.

2 Change directory to the top level on the media, for example:

# cd /mnt/cdrom/dist_arch

Installing Storage Foundation using the web-based installer

Obtaining a security exception on Mozilla Firefox

49

3 Start the Veritas XPortal Server process xprtlwid

, on the installation server:

# ./webinstaller start

The webinstaller script displays a URL. Note this URL.

Note: If you do not see the URL, please check your firewall and iptables settings.

If you have configured a firewall, ensure that the firewall settings allow access to the port 14172. You can alternatively use the -port option to use a free port instead.

You can use the following command to display the details about ports used by webinstaller and its status:

# ./webinstaller status

4 On the administrative server, start the web browser.

5 Navigate to the URL that the script displayed.

6 Certain browsers may display the following message:

Secure Connection Failed

Obtain a security exception for your browser.

When you are prompted, enter root and root's password of the installation server.

7 Log in as superuser.

Obtaining a security exception on Mozilla Firefox

You may need to get a security exception on Mozilla Firefox.

The following instructions are general. They may change because of the rapid release cycle of Mozilla browsers.

To obtain a security exception

1 Click Or you can add an exception link.

2 Click I Understand the Risks, or You can add an exception.

3 Click Get Certificate button.

4 Uncheck Permanently Store this exception checkbox (recommended).

Installing Storage Foundation using the web-based installer

Performing a preinstallation check with the web-based installer

50

5 Click Confirm Security Exception button.

6 Enter root in User Name field and root password of the web server in the

Password field.

Performing a preinstallation check with the web-based installer

This section describes performing a preinstallation check with the web-based installer.

To perform a preinstallation check

1 Start the web-based installer.

See

“Starting the web-based installer”

on page 48.

2 On the Select a task and a product page, select Perform a Pre-installation

Check from the Task drop-down list.

3 Select Storage Foundation from the Product drop-down list, and click Next.

4 Indicate the systems on which to perform the precheck. Enter one or more system names, separated by spaces. Click Next.

5 The installer performs the precheck and displays the results.

6 If the validation completes successfully, click Next. The installer prompts you to begin the installation. Click Yes to install on the selected system. Click No to install later.

7 Click Finish. The installer prompts you for another task.

Installing SF with the web-based installer

This section describes installing SF with the Symantec web-based installer.

To install SF using the web-based installer

1 Perform preliminary steps.

See

“Performing a preinstallation check with the web-based installer”

on page 50.

2 Start the web-based installer.

See

“Starting the web-based installer”

on page 48.

3 Select Install a Product from the Task drop-down list.

4 Select Storage Foundation from the Product drop-down list, and click Next.

Installing Storage Foundation using the web-based installer

Installing SF with the web-based installer

51

5 On the License agreement page, read the End User License Agreement (EULA).

To continue, select Yes, I agree and click Next.

6 Choose minimal, recommended, or all RPMs. Click Next.

7 Indicate the systems where you want to install. Separate multiple system names with spaces. Click Next.

8 If you have not yet configured a communication mode among systems, you have the option to let the installer configure ssh or rsh. If you choose to allow this configuration, select the communication mode and provide the superuser passwords for the systems.

9 After the validation completes successfully, click Next to install SF on the selected system.

10 After the installation completes, you must choose your licensing method.

On the license page, select one of the following radio buttons:

■ Enable keyless licensing and complete system licensing later

Note: The keyless license option enables you to install without entering a key. However, to ensure compliance, you must manage the systems with a management server.

For more information, go to the following website: http://go.symantec.com/sfhakeyless

Click Next

Complete the following information:

Choose whether you want to install Standard or Enterprise mode.

Choose whether you want to enable the Symantec Volume Replicator.

Choose whether you want to enable File Replicator.

Click Next.

■ Enter a valid license key

If you have a valid license key, input the license key and click Next.

Installing Storage Foundation using the web-based installer

Installing SF with the web-based installer

52

11 For Storage Foundation, click Next. If the installer prompts you to restart the system, then restart the system and invoke the web-based installer again for configuration. If the installer does not prompt you to restart the system, then it completes the configuration and starts the product processes.

Note that you are prompted to configure only if the product is not yet configured.

If you select n, you can exit the installer. You must configure the product before you use SF.

After the installation completes, the installer displays the location of the log and summary files. If required, view the files to confirm the installation status.

12 To configure Symantec Storage Foundation, start the web-based installer and select Configure a product. Click the OK button. The installers checks for updates. Click the Next button.

The installer displays the save location for the task log files, summary file, and response file.

Click the Finish button.

13 If you are prompted, enter the option to specify whether you want to send your installation information to Symantec.

Installation procedures and diagnostic information were saved in the log files under directory

/var/tmp/installer-<platform>-<uuid>. Analyzing this information helps Symantec discover and fix failed operations performed by the installer. Would you like to send the information about this installation to Symantec to help improve installation in the future? [y,n,q,?]

Click Finish.

Chapter

8

Automated installation using response files

This chapter includes the following topics:

Installing SF using response files

Response file variables to install Storage Foundation

Sample response file for SF installation

Configuring SF using response files

Response file variables to configure Storage Foundation

Installing SF using response files

Typically, you can use the response file that the installer generates after you perform

SF installation on a system to install SF on other systems. You can also create a response file using the -makeresponsefile option of the installer.

# ./installer -makeresponsefile

See

“About the script-based installer”

on page 41.

To install SF using response files

1 Make sure the systems where you want to install SF meet the installation requirements.

2 Make sure that the preinstallation tasks are completed.

3 Copy the response file to the system where you want to install SF.

4 Edit the values of the response file variables as necessary.

Automated installation using response files

Response file variables to install Storage Foundation

54

5 Mount the product disc and navigate to the directory that contains the installation program.

6 Start the installation from the system to which you copied the response file.

For example:

# ./installer -responsefile /tmp/response_file

# ./installsf -responsefile /tmp/response_file

Where /tmp/response_file is the response file’s full path name.

7 Complete the SF post-installation tasks.

For instructions, see the chapter Performing post-installation and configuration

tasks in this document.

Response file variables to install Storage Foundation

Table 8-1

lists the response file variables that you can define to install SF.

Table 8-1 Response file variables for installing SF

Variable

CFG{opt}{install}

CFG{opt}{installallpkgs} or

CFG{opt}{installrecpkgs} or

CFG{opt}{installminpkgs}

Description

Installs SF RPMs. Configuration can be performed at a later time using the -configure option.

List or scalar: scalar

Optional or required: optional

Instructs the installer to install SF RPMs based on the variable that has the value set to 1:

■ installallpkgs: Installs all RPMs installrecpkgs: Installs recommended RPMs installminpkgs: Installs minimum RPMs

Note: Set only one of these variable values to 1. In addition to setting the value of one of these variables, you must set the variable CFG{opt}{install} to 1.

List or scalar: scalar

Optional or required: required

Automated installation using response files

Response file variables to install Storage Foundation

55

Table 8-1

Variable

CFG{accepteula}

Response file variables for installing SF (continued)

CFG{opt}{vxkeyless}

Description

Specifies whether you agree with the EULA.pdf file on the media.

List or scalar: scalar

Optional or required: required

Installs the product with keyless license.

List or scalar: scalar

Optional or required: optional

CFG{opt}{license}

CFG{keys}{hostname}

CFG{systems}

CFG{prod}

CFG{opt}{keyfile}

Installs the product with permanent license.

List or scalar: scalar

Optional or required: optional

List of keys to be registered on the system if the variable

CFG{opt}{vxkeyless} is set to 0 or if the variable

CFG{opt}{licence} is set to 1.

List or scalar: scalar

Optional or required: optional

List of systems on which the product is to be installed or uninstalled.

List or scalar: list

Optional or required: required

Defines the product to be installed or uninstalled.

List or scalar: scalar

Optional or required: required

Defines the location of an ssh keyfile that is used to communicate with all remote systems.

List or scalar: scalar

Optional or required: optional

Automated installation using response files

Sample response file for SF installation

56

Table 8-1

Variable

CFG{opt}{tmppath}

Response file variables for installing SF (continued)

Description

Defines the location where a working directory is created to store temporary files and the RPMs that are needed during the install. The default location is /var/tmp.

List or scalar: scalar

Optional or required: optional

CFG{opt}{updatekeys}

CFG{opt}{rsh}

CFG{opt}{logpath}

CFG{opt}{prodmode}

Updates the keyless license to the current version.

List or scalar: scalar

Optional or required: optional

Defines that rsh must be used instead of ssh as the communication method between systems.

List or scalar: scalar

Optional or required: optional

Mentions the location where the log files are to be copied.

The default location is /opt/VRTS/install/logs.

List or scalar: scalar

Optional or required: optional

List of modes for product

List or scalar: list

Optional or required: optional

Sample response file for SF installation

The following example shows a response file for installing Storage Foundation.

our %CFG;

$CFG{accepteula}=1;

$CFG{opt}{configure}=1;

$CFG{opt}{install}=1;

$CFG{opt}{installrecpkgs}=1;

$CFG{opt}{prodmode}="SF Enterprise";

$CFG{opt}{updatekeys}=1;

$CFG{opt}{vxkeyless}=1;

$CFG{prod}="SF62";

Automated installation using response files

Configuring SF using response files

57

$CFG{systems}=[ qw(cdgv240a) ];

1;

Configuring SF using response files

Typically, you can use the response file that the installer generates after you perform

SF configuration on one system to configure SF on other systems. You can also create a response file using the -makeresponsefile option of the installer.

# ./installer -makeresponsefile -configure

# ./installsf -makeresponsefile -configure

To configure SF using response files

1 Make sure the SF RPMs are installed on the systems where you want to configure SF.

2 Copy the response file to the system where you want to configure SF.

3 Edit the values of the response file variables as necessary.

To configure optional features, you must define appropriate values for all the response file variables that are related to the optional feature.

See

“Response file variables to configure Storage Foundation”

on page 57.

4 Start the configuration from the system to which you copied the response file.

For example:

# /opt/VRTS/install/installsf<version>

-responsefile /tmp/response_file

Where

<version> is the specific release version, and

/tmp/response_file is the response file’s full path name.

See

“About the script-based installer”

on page 41.

Response file variables to configure Storage

Foundation

Table 8-2

lists the response file variables that you can define to configure SF.

Automated installation using response files

Response file variables to configure Storage Foundation

58

Table 8-2

Variable

CFG{opt}{configure}

CFG{accepteula}

Response file variables specific to configuring Storage Foundation

List or Scalar

Scalar

Scalar

Description

Performs the configuration if the

RPMs are already installed.

(Required)

Set the value to 1 to configure SF.

Specifies whether you agree with

EULA.pdf on the media.

(Required)

CFG{systems}

CFG{prod}

CFG{opt}{keyfile}

List

Scalar

Scalar

List of systems on which the product is to be configured.

(Required)

Defines the product to be configured.

The value is SF62 for SF.

(Required)

Defines the location of an ssh keyfile that is used to communicate with all remote systems.

(Optional)

CFG{opt}{rsh}

CFG{opt}{logpath}

Scalar

Scalar

Defines that rsh must be used instead of ssh as the communication method between systems.

(Optional)

Mentions the location where the log files are to be copied. The default location is /opt/VRTS/install/logs.

Note: The installer copies the response files and summary files also to the specified logpath location.

(Optional)

Automated installation using response files

Response file variables to configure Storage Foundation

59

Table 8-2

Variable

CFG{uploadlogs}

Response file variables specific to configuring Storage Foundation

(continued)

List or Scalar

Scalar

Description

Defines a Boolean value 0 or 1.

The value 1 indicates that the installation logs are uploaded to the

Symantec website.

The value 0 indicates that the installation logs are not uploaded to the Symantec website.

(Optional)

Chapter

9

Installing Storage

Foundation using operating system-specific methods

This chapter includes the following topics:

About installing SF using operating system-specific methods

Installing SF using Kickstart

Sample Kickstart configuration file

Installing Storage Foundation using yum

Installing SF using the Red Hat Satellite server

About installing SF using operating system-specific methods

On Linux, you can install SF using the following methods:

■ You can install SF using Kickstart. Kickstart is supported for Red Hat Enterprise

Linux 6 (RHEL6) and Red Hat Enterprise Linux 7 (RHEL7).

See

“Installing SF using Kickstart”

on page 61.

■ You can install SF using yum. yum is supported for Red Hat Enterprise Linux 6

(RHEL6) and Red Hat Enterprise Linux 7 (RHEL7).

See

“Installing Storage Foundation using yum”

on page 64.

Installing Storage Foundation using operating system-specific methods

Installing SF using Kickstart

61

■ You can install SF using the Red Hat Satellite server. Red Hat Satellite server is supported for Red Hat Enterprise Linux 6 (RHEL6) and Red Hat Enterprise

Linux 7 (RHEL7).

See

“Installing SF using the Red Hat Satellite server”

on page 69.

Installing SF using Kickstart

You can install SF using Kickstart. Kickstart is supported for Red Hat Enterprise

Linux operating system.

To install SF using Kickstart

1 Create a directory for the Kickstart configuration files.

# mkdir /kickstart_files/

2 Generate the Kickstart configuration files. The configuration files have the extension

.ks

. Do one of the following:

■ To generate configuration files, enter the following command:

# ./installer -kickstart /kickstart_files/

The system lists the files.

If you only need to install Storage Foundation RPMs during the Kickstart operating system installation, that is, you do not need to generate the .ks

configuration file for Symantec Cluster Server RPMs, run the installsf script. Enter the following:

# ./installsf -kickstart /kickstart_files/

The output includes the following:

The kickstart script for SF is generated at

/kickstart_files/kickstart_sf62.ks

3 Set up an NFS exported location which the Kickstart client can access. For example, if /nfs_mount_kickstart is the directory which has been NFS exported, the NFS exported location may look similar to the following:

# cat /etc/exports

/nfs_mount_kickstart * (rw,sync,no_root_squash)

4 Copy the rpms directory from the installation media to the NFS location.

Installing Storage Foundation using operating system-specific methods

Sample Kickstart configuration file

62

5 Verify the contents of the directory.

# ls /nfs_mount_kickstart/

6 In the SF Kickstart configuration file, modify the

BUILDSRC variable to point to the actual NFS location. The variable has the following format:

BUILDSRC="hostname_or_ip:/nfs_mount_kickstart"

7 Append the entire modified contents of the Kickstart configuration file to the operating system ks.cfg

file.

8 Launch the Kickstart installation for the operating system.

9 After the operating system installation is complete, check the file

/var/tmp/kickstart.log

for any errors that are related to the installation of

RPMs and product installer scripts.

10 Verify that all the product RPMs have been installed. Enter the following command:

# rpm -qa | grep -i vrts

11 If you do not find any installation issues or errors, configure the product stack.

Enter the following command:

# /opt/VRTS/install/installsf<version> -configure node1 node2

Where <version> is the specific release version.

See

“About the script-based installer”

on page 41.

Sample Kickstart configuration file

The following is a sample RedHat Enterprise Linux 6 (RHEL6) Kickstart configuration file.

# The packages below are required and will be installed from OS installation media automatically # during the automated installation of products in the DVD, if they have not been installed yet.

%packages systemd-libs.i686

device-mapper device-mapper-libs parted

Installing Storage Foundation using operating system-specific methods

Sample Kickstart configuration file

63 libgcc.i686

ed ksh nss-softokn-freebl.i686

glibc.i686

libstdc++.i686

audit-libs.i686

cracklib.i686

libselinux.i686

pam.i686

libattr.i686

libacl.i686

%end

%post --nochroot

# Add necessary scripts or commands here to your need

# This generated kickstart file is only for the automated installation of products in the DVD

PATH=$PATH:/sbin:/usr/sbin:/bin:/usr/bin export PATH

#

# Notice:

# * You do not have to change the following scripts

#

# define path varibles

ROOT=/mnt/sysimage

BUILDDIR="${ROOT}/build"

RPMDIR="${BUILDDIR}/rpms"

# define log path

KSLOG="${ROOT}/var/tmp/kickstart.log" echo "==== Executing kickstart post section: ====" >> ${KSLOG} mkdir -p ${BUILDDIR} mount -t nfs -o nolock,vers=3 ${BUILDSRC} ${BUILDDIR} >> ${KSLOG} 2>&1

# Install the RPMs in the following order.

for RPM in VRTSperl VRTSvlic VRTSspt VRTSvxvm VRTSaslapm VRTSob

VRTSvxfs VRTSfsadv VRTSfssdk VRTSdbed VRTSodm VRTSsfmh VRTSsfcpi62

Installing Storage Foundation using operating system-specific methods

Installing Storage Foundation using yum

64 do done echo "Installing package -- $RPM" >> ${KSLOG} rpm -U -v --root ${ROOT} ${RPMDIR}/${RPM}-* >> ${KSLOG} 2>&1 umount ${BUILDDIR}

CALLED_BY=KICKSTART ${ROOT}/opt/VRTS/install/bin/

UXRT62/add_install_scripts >> ${KSLOG} 2>&1 echo "==== Completed kickstart file ====" >> ${KSLOG} exit 0

%end

Installing Storage Foundation using yum

You can install SF using yum. yum is supported for Red Hat Enterprise operating system.

To install SF using yum

1 Run the installsf -pkginfo command to get SF RPMs.

# ./installsf -pkginfo

2 Add the SF RPMs into the yum repository. You can add SF RPMs into either a new repository or an existing repository with other RPMs. Use the createrepo command to create or update the repository. The operating system RPM createrepo-ver-rel.noarch.rpm

provides the command.

■ To create the new repository /path/to/new/repository/ for SF RPMs

1.

Create an empty directory, for example: /path/to/new/repository. The yum client systems should be able to access the directory with the HTTP, FTP, or file protocols.

# rm -rf /path/to/new/repository

# mkdir -p /path/to/new/repository

Installing Storage Foundation using operating system-specific methods

Installing Storage Foundation using yum

65

2.

Copy all the SF RPMs into /path/to/new/repository/.

# cp -f VRTSvlic-* VRTSperl-* ... VRTSsfcpi62-*\

/path/to/new/repository

3.

Use the createrepo command to create the repository.

# /usr/bin/createrepo /path/to/new/repository

Output resembles:

27/27 - VRTSsfcpi62-6.2.0.000-GENERIC.noarch.rpm

Saving Primary metadata

Saving file lists metadata

Saving other metadata

4.

The metadata for this repository is created in /path/to/new/repository/repodata.

■ To use an existing repository in /path/to/existing/repository/ for SF

RPMs

1.

Copy all the SF RPMs into /path/to/existing/repository/. The yum client systems should be able to access the directory with the HTTP, FTP, or file protocols.

# cp -f VRTSvlic-* VRTSperl-* ... VRTSsfcpi62-*\

/path/to/existing/repository

2.

Use the createrepo command with the --update option to update the repository's metadata.

# createrepo --update /path/to/existing/repository

Output resembles:

27/27 * VRTSsfcpi62-6.2.0.000-GENERIC.noarch.rpm

Saving Primary metadata

Saving file lists metadata

Saving other metadata

3.

The metadata in /path/to/existing/repository/repodata is updated for the newly added RPMs.

■ To create a RPM group for SF RPMs when the repository is created or updated (optional)

Installing Storage Foundation using operating system-specific methods

Installing Storage Foundation using yum

66

1.

Create an XML file, which you can name SF_group.xml in the repository directory. In the file specify the name, the ID, the RPM list, and other information for the group. You can generate this XML file using the installer with the option

-yumgroupxml . An example of this XML file for SF is:

# cat SF_group.xml

<comps>

<group>

<id>SF62</id>

<name>SF62</name>

<default>true</default>

<description>RPMs of SF 6.2.0.000</description>

<uservisible>true</uservisible>

<packagelist>

<packagereq type="default">VRTSvlic</packagereq>

<packagereq type="default">VRTSperl</packagereq>

... [other RPMs for SF]

<packagereq type="default">VRTSsfcpi62</packagereq>

</packagelist>

</group>

</comps>

2.

Create the group when the repository is created or updated.

# createrepo -g SF_group.xml /path/to/new/repository/

Or

# createrepo -g SF_group.xml --update /path/to/existing\

/repository/

Refer to the Red Hat Enterpirse Linux Deployment Guide for more information on yum repository configuration.

3 Configure a yum repository on a client system.

■ Create a

.repo

file under

/etc/yum.repos.d/

. An example of this

.repo

file for SF is:

# cat /etc/yum.repos.d/SF.repo

[repo-SF] name=Repository for SF baseurl=file:///path/to/repository/ enabled=1 gpgcheck=0

Installing Storage Foundation using operating system-specific methods

Installing Storage Foundation using yum

67

The values for the baseurl attribute can start with http://, ftp://, or file:///.

The URL you choose needs to be able to access the repodata directory.

It also needs to access all the SF RPMs in the repository that you create or update.

Check the yum configuration. List SF RPMs.

# yum list 'VRTS*'

Available Packages

VRTSperl.x86_64

VRTSsfcpi62.noarch

VRTSvlic.x86_64

...

5.16.1.4-RHEL5.2

6.2.0.000-GENERIC

3.02.62.010-0 repo-SF repo-SF repo-SF

The SF RPMs may not be visible immediately if:

■ The repository was visited before the SF RPMs were added, and

■ The local cache of its metadata has not expired.

To eliminate the local cache of the repositories' metadata and get the latest information from the specified baseurl

, run the following commands:

# yum clean expire-cache

# yum list 'VRTS*'

Refer to the Red Hat Enterpirse Linux Deployment Guide for more information on yum repository configuration.

4 Install the RPMs on the target systems.

■ To install all the RPMs

1.

Specify each RPM name as its yum equivalent. For example:

# yum install VRTSvlic VRTSperl ... VRTSsfcpi62

2.

Specify all of the SF RPMs using its RPM glob. For example:

# yum install 'VRTS*'

Installing Storage Foundation using operating system-specific methods

Installing Storage Foundation using yum

68

3.

Specify the group name if a group is configured for SF's RPMs. In this example, the group name is SF62:

# yum install @SF62

Or

# yum groupinstall SF62

■ To install one RPM at a time

1.

Run the installsf -pkginfo command to determine RPM installation order.

# ./installsf -pkginfo

The following Symantec Storage Foundation RPMs must be installed in the specified order to achieve full functionality. The RPMs listed are all the RPMs offered by the Symantec Storage Foundation product.

RPMs: VRTSperl VRTSvlic VRTSspt VRTSvxvm VRTSaslapm VRTSob

VRTSvxfs VRTSfsadv VRTSfssdk VRTSdbed VRTSodm

VRTSsfmh VRTSsfcpi62

The following Symantec Storage Foundation RPMs must be installed in the specified order to achieve recommended functionality. The RPMs listed are the recommended RPMs for Symantec Storage Foundation offering basic and some advanced functionality for the product.

RPMs: VRTSperl VRTSvlic VRTSspt VRTSvxvm VRTSaslapm VRTSob

VRTSvxfs VRTSfsadv VRTSdbed VRTSodm VRTSsfmh VRTSsfcpi62

The following Symantec Storage Foundation RPMs must be installed in the specified order to achieve basic functionality. The RPMs listed provide minimum footprint of the Symantec Storage Foundation product.

RPMs: VRTSperl VRTSvlic VRTSvxvm VRTSaslapm VRTSvxfs

VRTSfsadv VRTSsfcpi62

Installing Storage Foundation using operating system-specific methods

Installing SF using the Red Hat Satellite server

69

2.

Use the same order as the output from the installsf -pkginfo command:

# yum install VRTSperl

# yum install VRTSvlic

...

# yum install VRTSsfcpi62

5 After you install all the RPMs, use the

/opt/VRTS/install/installsf<version> script to license, configure, and start the product.

Where <version> is the specific release version.

See

“About the script-based installer”

on page 41.

If the VRTSsfcpi62 RPM is installed before you use yum to install SF, the RPM is not upgraded or uninstalled. If the

/opt/VRTS/install/installsf<release_version> script is not created properly, use the

/opt/VRTS/install/bin/UXRT62/add_install_scripts script to create the installsf or uninstallsf scripts after all the other SF RPMs are installed. For example, your output may be similar to the following, depending on the products you install:

# /opt/VRTS/install/bin/UXRT62/add_install_scripts

Creating install/uninstall scripts for installed products

Creating /opt/VRTS/install/installvcs62 for UXRT62

Creating /opt/VRTS/install/uninstallvcs62 for UXRT62

Creating /opt/VRTS/install/installdmp62 for UXRT62

Creating /opt/VRTS/install/uninstalldmp62 for UXRT62

Creating /opt/VRTS/install/installfs62 for UXRT62

Creating /opt/VRTS/install/uninstallfs62 for UXRT62

Creating /opt/VRTS/install/installsf62 for UXRT62

Creating /opt/VRTS/install/uninstallsf62 for UXRT62

Creating /opt/VRTS/install/installvm62 for UXRT62

Creating /opt/VRTS/install/uninstallvm62 for UXRT62

Installing SF using the Red Hat Satellite server

You can install SF using the Red Hat Satellite server. Red Hat Satellite is supported for Red Hat Enterprise Linux operating system. You can install RPMs and rolling patches on the systems which the Red Hat Satellite server manages.

Red Hat Satellite server is a systems management solution. It lets you:

Installing Storage Foundation using operating system-specific methods

Installing SF using the Red Hat Satellite server

70

Inventory the hardware and the software information of your systems.

Install and update software on systems.

Collect and distribute custom software RPMs into manageable groups.

Provision (Kickstart) systems.

Manage and deploy configuration files to systems.

Monitor your systems.

Provision virtual guests.

■ Start, stop, and configure virtual guests.

In a Red Hat Satellite server, you can manage the system by creating a channel.

A Red Hat Satellite channel is a collection of software RPMs. Using channels, you can segregate the RPMs by defining some rules. For instance, a channel may contain RPMs only from a specific Red Hat distribution. You can define channels according to your own requirement. You can create a channel that contains SF

RPMs for custom usage in your organization's network.

Channels are of two types:

Base channel

A base channel consists of RPMs based on a specific architecture and Red Hat

Enterprise Linux release.

Child channel

A child channel is a channel which is associated with a base channel that contains extra custom RPMs like SF.

A system can subscribe to only one base channel and multiple child channels of its base channel. The subscribed system can only install or update the RPMs that are available through its satellite channels.

For more information, see the Red Hat Satellite5.6 User Guide.

Using Red Hat Satellite server to install SF products

You can use the Red Hat Satellite server to install SF products on your system.

To use Red Hat Satellite server to install SF products

1 Set the base channel, child channel, and target system by following the Red

Hat Satellite documentation. You need to ensure that:

The base channel consists of RPMs based on RHEL6.3, RHEL6.4,

RHEL6.5, or the RHEL7 release

■ The child channel consists of SF RPMs or patches.

Installing Storage Foundation using operating system-specific methods

Installing SF using the Red Hat Satellite server

71

■ The target system is registered to the Red Hat Satellite.

2 Log on to the Red Hat Satellite admin page. Select the Systems tab. Click on the target system.

3 Select Alter Channel Subscriptions to alter the channel subscription of the target system.

4 Select the channel which contains the repository of SF.

5 Enter the following command to check the YUM repository on the target system.

# yum repolist

6 Enter the following command to install the SF RPMs using YUM:

# yum install @SF62

7 Enter the following command to generate the script of the installer:

# /opt/VRTS/install/bin/UXRT62/add_install_scripts

8 Enter the following command to configure SF using the installer:

# ./installsf62 -configure

Chapter

10

Configuring Storage

Foundation

This chapter includes the following topics:

Configuring Storage Foundation using the installer

Configuring Storage Foundation manually

Configuring SFDB

Configuring Storage Foundation using the installer

You can use the installer to configure Storage Foundation, although it requires minimal configuration. You do need to start it.

To start Storage Foundation

1 Go to the /opt/VRTS/install/ installation directory.

2 Run the installer command with the configure option.

# ./installsf62 -configure

Configuring Storage Foundation manually

You can manually configure different products within Storage Foundation.

Configuring Storage Foundation

Configuring Storage Foundation manually

73

Configuring Veritas Volume Manager

Use the following procedures to configure Veritas Volume Manager. If you have installed and configured VxVM using the product installer, you do not need to complete the procedures in this section.

For information on setting up VxVM disk groups and volumes after installation, see

"Configuring Veritas Volume Manager" in the Symantec Storage Foundation

Administrator’s Guide.

Configuring Veritas File System

After installing Veritas File System, you can create a file system on a disk slice or

Veritas Volume Manager volume with the mkfs command. Before you can use this file system, you must mount it with the mount command. You can unmount the file system later with the umount command. A file system can be automatically mounted at system boot time if you add an entry for it in the following file:

/etc/fstab

The Symantec-specific commands are described in the Symantec Storage

Foundation guides and online manual pages.

See the Symantec Storage Foundation Administrator's Guide.

Loading and unloading the file system module

The vxfs file system module automatically loads on the first reference to a VxFS file system; this occurs when a user tries to mount a VxFS file system.

In some instances, you may find it efficient to load the file system module manually.

For example, some larger class systems can have many dual interface I/O cards with multiple disk chains attached. The device interrogation process when such a system is rebooted can be very time consuming, so to avoid doing a reboot, use the modprobe command to load the vxfs module:

# modprobe vxfs ; modprobe vxportal ; modprobe fdd

Do not use the insmod command to load the vxfs module as insmod does not examine the module configuration file

/etc/modprobe.conf

.

To determine if the modules successfully loaded, use the lsmod command as shown here:

# lsmod | grep vxportal vxportal 2952 vxfs 3427960

0

0 fdd vxportal

Configuring Storage Foundation

Configuring SFDB

74

# lsmod | grep fdd fdd vxfs

# lsmod | grep vxfs vxfs

67212

3427960

0

0

(unused)

[fdd vxportal]

3427960 0 [fdd vxportal]

The first field in the output is the module name. You can unload the modules by entering:

# rmmod fdd

# rmmod vxportal

# rmmod vxfs

The rmmod command fails if there are any mounted VxFS file systems. To determine if any VxFS file systems are mounted, enter:

# df -T | grep vxfs

Configuring SFDB

By default, SFDB tools are disabled that is the vxdbd daemon is not configured.

You can check whether SFDB tools are enabled or disabled using the /opt/VRTS/bin/sfae_config status command.

To enable SFDB tools

1 Log in as root.

2 Run the following command to configure and start the vxdbd daemon. After you perform this step, entries are made in the system startup so that the daemon starts on a system restart.

# /opt/VRTS/bin/sfae_config enable

To disable SFDB tools

1 Log in as root.

2 Run the following command:

#

/opt/VRTS/bin/sfae_config disable

Section

3

Managing your Symantec deployments

Chapter 11. Performing centralized installations using the Deployment Server

Chapter

11

Performing centralized installations using the

Deployment Server

This chapter includes the following topics:

About the Deployment Server

Deployment Server overview

Installing the Deployment Server

Setting up a Deployment Server

Setting deployment preferences

Specifying a non-default repository location

Downloading the most recent release information

Loading release information and patches on to your Deployment Server

Viewing or downloading available release images

Viewing or removing repository images stored in your repository

Deploying Symantec product updates to your environment

Finding out which releases you have installed, and which upgrades or updates you may need

Defining Install Bundles

Creating Install Templates

Performing centralized installations using the Deployment Server

About the Deployment Server

77

Deploying Symantec releases

Connecting the Deployment Server to SORT using a proxy server

About the Deployment Server

The Deployment Server makes it easier to install or upgrade SFHA releases from a central location. The Deployment Server lets you store multiple release images and patches in one central location and deploy them to systems of any supported

UNIX or Linux operating system (6.1 or later).

Note: The script-based installer for version 6.1 and higher supports installations from one operating system node onto a different operating system. Therefore, heterogeneous push installations are supported for 6.1 and higher releases only.

Push installations for product versions 5.1, 6.0, or 6.0.1 releases must be executed from a system that is running the same operating system as the target systems. In order to perform push installations for product versions 5.1, 6.0, or 6.0.1 releases on multiple platforms, you must have a separate Deployment Server for each operating system.

The Deployment Server lets you do the following as described in

Table 11-1 .

Table 11-1 Deployment Server functionality

Feature Description

Manage repository images

View available SFHA releases.

Download maintenance and patch release images from the

Symantec Operations Readiness Tools (SORT) website into a repository.

Load the downloaded release image files from FileConnect and

SORT into the repository.

View and remove the release image files that are stored in the repository.

Version check systems

Discover RPMs and patches installed on your systems and informs you of the product and version installed

Identify base, maintenance, and patch level upgrades to your system and to download maintenance and patch releases.

Query SORT for the most recent updates.

Performing centralized installations using the Deployment Server

Deployment Server overview

78

Table 11-1 Deployment Server functionality (continued)

Feature Description

Install or upgrade systems

Install base, maintenance, or patch level releases.

Install SFHA from any supported UNIX or Linux operating system to any other supported UNIX or Linux operating system.

Automatically load the script-based installer patches that apply to that release.

Install or upgrade an Install Bundle that is created from the

Define/Modify Install Bundles menu.

Install an Install Template that is created from the Create Install

Templates menu.

Define or modify

Install Bundles

Create Install

Templates

Define or modify Install Bundles and save them using the Deployment

Server.

Discover installed components on a running system that you want to replicate on to new systems.

Update metadata Download, load the release matrix updates, and product installer updates for systems behind a firewall.

This process happens automatically when you connect the Deployment

Server to the Internet, or it can be initiated manually. If the Deployment

Server is not connected to the Internet, then the Update Metadata option is used to upload current metadata.

Set preferences Define or reset program settings.

Connecting the

Deployment Server to SORT using a proxy server

Use a proxy server, a server that acts as an intermediary for requests from clients, for connecting the Deployment Server to the Symantec

Operations Readiness Tools (SORT) website.

Note: The Deployment Server is available only from the command line. The

Deployment Server is not available for the web-based installer.

Note: Many of the example outputs used in this chapter are based on Red Hat

Enterprise Linux.

Deployment Server overview

After obtaining and installing the Deployment Server and defining a central repository, you can begin managing your deployments from that repository. You

Performing centralized installations using the Deployment Server

Installing the Deployment Server

79 can load and store product images for Symantec products back to version 5.1 in your Deployment Server. The Deployment Server is a central installation server for storing and managing your product updates.

Setting up and managing your repository involves the following tasks:

Installing the Deployment Server.

See

“Installing the Deployment Server”

on page 79.

Setting up a Deployment Server.

See

“Setting up a Deployment Server”

on page 80.

Finding out which products you have installed, and which upgrades or updates you may need.

See

“Viewing or downloading available release images”

on page 87.

Adding release images to your Deployment Server.

See

“Viewing or downloading available release images”

on page 87.

Removing release images from your Deployment Server.

See

“Viewing or removing repository images stored in your repository”

on page 92.

Defining or modifying Install Bundles to manually install or upgrade a bundle of two or more releases.

See

“Defining Install Bundles”

on page 97.

■ Creating Install Templates to discover installed components on a system that you want to replicate to another system.

See

“Creating Install Templates”

on page 102.

Later, when your repository is set up, you can use it to deploy Symantec products to other systems in your environment.

See

“Deploying Symantec product updates to your environment”

on page 94.

See

“Deploying Symantec releases”

on page 104.

Installing the Deployment Server

You can obtain the Deployment Server by either:

■ Installing the Deployment Server manually.

■ Running the Deployment Server after installing at least one Symantec 6.2

product.

Performing centralized installations using the Deployment Server

Setting up a Deployment Server

80

Note: The

VRTSperl and the

VRTSsfcpi<version>

RPMs are included in all Storage

Foundation (SF) products, so installing any Symantec 6.2 product lets you access the Deployment Server.

To install the Deployment Server manually without installing a Symantec 6.2 product

1 Log in as superuser.

2 Mount the installation media.

See

“Mounting the product disc”

on page 38.

3 Move to the top-level directory on the disc.

# cd /mnt/cdrom/dist_arch where dist is rhel6, rhel7, or sles11, and arch is x86_64 for RHEL and SLES.

4 Navigate to the following directory:

# cd rpms

5 Run the following command to install the

VRTSperl and the

VRTSsfcpi<version>

RPMs:

# rpm -ivh VRTSperl*.rpm VRTSsfcpi<version>*.rpm

To run the Deployment Server

1 Log in as superuser.

2 Navigate to the following directory:

# cd /opt/VRTS/install

3 Run the Deployment Server.

# ./deploy_sfha

Setting up a Deployment Server

Symantec recommends that you create a dedicated Deployment Server to manage your product updates.

A Deployment Server is useful for doing the following tasks:

■ Storing release images for the latest upgrades and updates from Symantec in a central repository directory.

Performing centralized installations using the Deployment Server

Setting up a Deployment Server

81

Installing and updating systems directly by accessing the release images that are stored within a central repository.

Defining or modifying Install Bundles for deploying a bundle of two or more releases.

Discovering installed components on a system that you want to replicate to another system.

■ Installing Symantec products from the Deployment Server to systems running any supported platform.

■ Creating a file share on the repository directory provides a convenient, central location from which systems running any supported platform can install the latest

Symantec products and updates.

Create a central repository on the Deployment Server to store and manage the following types of Symantec releases:

Base releases. These major releases and minor releases are available for all

Symantec products. They contain new features, and you can download them from FileConnect.

Maintenance releases. These releases are available for all Symantec products.

They contain bug fixes and a limited number of new features, and you can download them from the Symantec Operations Readiness Tools (SORT) website.

Patches. These releases contain fixes for specific products, and you can download them from the SORT website.

Note: All base releases and maintenance releases can be deployed using the install scripts that are included in the release. Before version 6.0.1, patches were installed manually. From the 6.0.1 release and onwards, install scripts are included with patch releases.

You can set up a Deployment Server with or without Internet access.

If you set up a Deployment Server that has Internet access, you can download maintenance releases and patches from Symantec directly. Then, you can deploy them to your systems.

Setting up a Deployment Server that has Internet access

If you set up a Deployment Server that does not have Internet access, you can download maintenance releases and patches from Symantec on another system that has Internet access. Then, you can load the images onto the Deployment

Server separately.

Setting up a Deployment Server that does not have Internet access

Performing centralized installations using the Deployment Server

Setting up a Deployment Server

82

Setting up a Deployment Server that has Internet access

Figure 11-1

shows a Deployment Server that can download product images directly from Symantec using the Deployment Server.

Figure 11-1 Example Deployment Server that has Internet access

Symantec

FileConnect/SORT

Repository

Download release images and metadata

Internet

Release images

Deployment

Server

Direct installation

Push installations

Setting up a Deployment Server that does not have Internet access

Figure 11-2

shows a Deployment Server that does not have Internet access. In this scenario, release images and metadata updates are downloaded from another system. Then, they are copied to a file location available to the Deployment Server, and loaded.

Performing centralized installations using the Deployment Server

Setting deployment preferences

83

Figure 11-2 Example Deployment Server that does not have Internet access

Outside Firewall Inside Firewall

Repository

Symantec

FileConnect/SORT

Release images

Download release images and metadata

Internet

Deployment

Server

Direct installation

Push installations

Release image files for base releases must be manually downloaded from

FileConnect and loaded in a similar manner.

Setting deployment preferences

You can set preferences for managing the deployment of products dating back to version 5.1.

Note: You can select option U (Terminology and Usage) to obtain more information about Deployment Server terminology and usage.

Performing centralized installations using the Deployment Server

Setting deployment preferences

84

To set deployment preferences

1 Launch the Deployment Server.

# /opt/VRTS/install/deploy_sfha

You see the following output:

Task Menu:

R) Manage Repository Images

V) Version Check Systems

I) Install/Upgrade Systems

B) Define/Modify Install Bundles

T) Create Install Templates

M) Update Metadata

S) Set Preferences

U) Terminology and Usage

?) Help

Q) Quit

Enter a Task: [R,M,V,S,I,U,B,?,T,Q]

2 Select option S, Set Preferences.

You see the following output:

Current Preferences:

Repository

Selected Platforms

Save Tar Files

Preference List:

/opt/VRTS/repository

N/A

N/A

1) Repository

2) Selected Platforms

3) Save Tar Files b) Back to previous menu

Select a preference to set: [1-3,b,q,?]

3 Do one of the following:

■ To set the default repository, enter 1. Then enter the name of the repository in which you want to store your downloads. For example, enter the following:

/opt/VRTS/install/ProductDownloads

If the specified repository replaces a previous repository, the installer asks if you want to move all your files into the new repository. To move your files to the new repository, enter y.

Performing centralized installations using the Deployment Server

Specifying a non-default repository location

85

To add or remove a platform, enter 2. You are provided selections for adding or deleting a platform. When a single platform is removed, it becomes N/A, which means that it is not defined. By default, all platforms are chosen.

Once you select to add or remove a platform, the platform is added or removed in the preferences file and the preference platforms are updated.

If only one platform is defined, no platform, architecture, distribution, and version selection menu is displayed.

To set the option for saving or removing tar files, enter 3. At the prompt, if you want to save the tar files after untarring them, enter y. Or, if you want to remove tar files after untarring them, enter n.

By default, the installer does not remove tar files after the releases have been untarred.

Specifying a non-default repository location

You can specify a repository location other than the default that has been set within the system preferences by using the command line option. The command line option is mainly used to install a release image from a different repository location. When you use the command line option, the designated repository folder is used instead of the default for the execution time of the script. Using the command line option does not override the repository preference set by the Set Preference menu item.

Note: When you specify a non-default repository, you are allowed only to view the repository (View/Remove Repository), and use the repository to install or upgrade

(Install/Upgrade Systems) on other systems.

To use the command line option to specify a non-default repository location

◆ At the command line, to specify a non-default repository location, enter the following:

# ./deploy_sfha -repository repository_path where repository_path is the location of the repository.

Downloading the most recent release information

Use one of the following methods to obtain a

.tar

file with the most recent release information:

Download a copy from the SORT website.

Run the Deployment Server from a system that has Internet access.

Performing centralized installations using the Deployment Server

Loading release information and patches on to your Deployment Server

86

To obtain a data file by downloading a copy from the SORT website

1 Download the .tar

file from the SORT site at: https://sort.symantec.com/support/related_links/offline-release-updates

2 Click on deploy_sfha.tar [Download], and save the file to your desktop.

To obtain a data file by running the Deployment Server from a system with Internet access

1 Run the Deployment Server. Enter the following:

# /opt/VRTS/install/deploy_sfha

2 Select option M, Update Metadata.

You see the following output:

The Update Metadata option is used to load release matrix updates on to systems that do not have an Internet connection with SORT (https://sort.symantec.com).

Your system has a connection with SORT and is able to receive updates.

No action is necessary unless you would like to create a file to update another Deployment Server system.

1) Download release matrix updates and installer patches

2) Load an update tar file b) Back to previous menu

Select the option: [1-2,b,q,?]

3 Select option 1, Download release matrix updates and installer patches.

Loading release information and patches on to your

Deployment Server

In this procedure, the Internet-enabled system is the system to which you downloaded the deploy_sfha.tar

file.

See

“Downloading the most recent release information”

on page 85.

Performing centralized installations using the Deployment Server

Viewing or downloading available release images

87

To load release information and patches on to your Deployment Server

1 On the Internet-enabled system, copy the deploy_sfha.tar

file you downloaded to a location accessible by the Deployment Server.

2 On the Deployment Server, change to the installation directory. For example, enter the following:

# cd /opt/VRTS/install/

3 Run the Deployment Server. Enter the following:

# ./deploy_sfha

4 Select option M, Update Metadata, and select option 2, Load an update tar

file. Enter the location of the deploy_sfha.tar

file (the installer calls it a

"meta-data tar file").

Enter the location of the meta-data tar file: [b]

(/opt/VRTS/install/deploy_sfha.tar)

For example, enter the location of the meta-data tar file:

/tmp/deploy_sfha.tar

Viewing or downloading available release images

You can use the Deployment Server to conveniently view or download available release images to be deployed on other systems in your environment.

Note: If you have Internet access, communication with the Symantec Operations

Readiness Tools (SORT) provides the latest release information. If you do not have

Internet access, static release matrix files are referenced, and the most recent updates may not be included.

See

“Loading release information and patches on to your Deployment Server”

on page 86.

Performing centralized installations using the Deployment Server

Viewing or downloading available release images

88

To view or download available release images

1 Launch the Deployment Server.

# /opt/VRTS/install/deploy_sfha

You see the following output:

Task Menu:

R) Manage Repository Images

V) Version Check Systems

I) Install/Upgrade Systems

B) Define/Modify Install Bundles

T) Create Install Templates

M) Update Metadata

S) Set Preferences

U) Terminology and Usage

?) Help

Q) Quit

Enter a Task: [R,M,V,S,I,U,B,?,T,Q]

2 Select option R, Manage Repository Images.

You see the following output:

1) View/Download Available Releases

2) View/Remove Repository Images

3) Load a Release Image b) Back to previous menu

Select the option you would like to perform [1-3,b,q,?]

Performing centralized installations using the Deployment Server

Viewing or downloading available release images

89

3 Select option 1, View/Download Available Releases, to view or download what is currently installed on your system.

You see a list of platforms and release levels.

To view or download available releases, the platform type and release level type must be selected.

1) AIX 5.3

3) AIX 7.1

5) RHEL5 x86_64

7) RHEL7 x86_64

9) SLES11 x86_64

11) Solaris 10 Sparc

13) Solaris 11 Sparc b) Back to previous menu

2)

4)

6)

8)

AIX 6.1

HP-UX 11.31

RHEL6 x86_64

SLES10 x86_64

10) Solaris 9 Sparc

12) Solaris 10 x64

14) Solaris 11 x64

Select the platform of the release to view/download [1-14,b,q]

4 Select the release level for which you want to get release image information.

Enter the platform you want.

You see options for the Symantec release levels.

1) Base

2) Maintenance

3) Patch b) Back to previous menu

Select the level of the <platform> releases to view/download

[1-3,b,q,?]

5 Select the number corresponding to the type of release you want to view (Base,

Maintenance, or Patch).

You see a list of releases available for download.

Available Maintenance releases for rhel6_x86_64: release_version SORT_release_name DL OBS AI rel_date size_KB

============================================================================

5.1SP1PR2RP2

5.1SP1PR2RP3

sfha-rhel6_x86_64-5.1SP1PR2RP2 sfha-rhel6_x86_64-5.1SP1PR2RP3 -

Y

Y

Y

Y

2011-09-28 145611

2012-10-02 153924

5.1SP1PR2RP4

5.1SP1PR3RP2

5.1SP1PR3RP3

sfha-rhel6_x86_64-5.1SP1PR2RP4 sfha-rhel6_x86_64-5.1SP1PR3RP2 sfha-rhel6_x86_64-5.1SP1PR3RP3 -

-

Y

Y

Y

Y

Y

2013-08-21 186859

2011-09-28 145611

2012-10-02 153924

Performing centralized installations using the Deployment Server

Viewing or downloading available release images

90

5.1SP1PR3RP4

6.0RP1

6.0.3

6.0.5

sfha-rhel6_x86_64-5.1SP1PR3RP4 Y 2013-08-21 186859 sfha-rhel6_x86_64-6.0RP1

sfha-rhel6_x86_64-6.0.3

sfha-rhel6_x86_64-6.0.5

-

-

-

-

Y

-

Y

Y

Y

2012-03-22 210076

2013-02-01 212845

2014-04-15 199143

6.1.1

sfha-rhel6_x86_64-6.1.1

Y 2014-07-24 208028

Enter the release_version to view details about a release or press 'Enter' to continue [b,q,?]

The following are the descriptions for the column headers:

■ release_version: The version of the release.

SORT_release_name: The name of the release, used when accessing

SORT ( https://sort.symantec.com

).

DL: An indicator that the release is present in your repository.

OBS: An indicator that the release is obsolete by another higher release.

AI: An indicator that the release has scripted install capabilities. All base and maintenance releases have auto-install capabilities. Patch releases with auto-install capabilities are available beginning with version 6.1.

Otherwise the patch requires a manual installation.

rel_date: The date the release is available.

■ size_KB: The file size of the release in kilobytes.

6 If you are interested in viewing more details about any release, type the release version. For example, enter the following:

6.0.3

You see the following output: release_version: 6.0.3

release_name: sfha-rhel6_x86_64-6.0.3

release_type: MR release_date: 2013-02-01 downloaded: Y install_path: rhel6_x86_64/installmr upload_location: ftp://ftp.veritas.com/pub/support/patchcentral

/Linux/6.0.3/sfha/sfha-rhel6_x86_64-6.0.3-patches.tar.gz

obsoletes: 6.0.1.200-fs,6.0.1.200-vm,6.0.1.300-fs obsoleted_by: None

Would you like to download this Maintenance Release? [y,n,q] (y) n

Enter the release_version to view the details about a release or press

'Enter' to continue [b,q,?]

Performing centralized installations using the Deployment Server

Viewing or downloading available release images

91

7 If you do not need to check detail information, you can press Enter.

You see the following question:

Would you like to download a rhel6_x86_64 Maintenance Release Image?

[y,n,q] (n) y

If you select a y, you see a menu of all releases that are not currently in the repository.

1) 5.1SP1PR2RP2

2) 5.1SP1PR2RP3

3) 5.1SP1PR2RP4

4) 5.1SP1PR3RP2

5) 5.1SP1PR3RP3

6) 5.1SP1PR3RP4

7) 6.0RP1

8) 6.0.3

9) 6.0.5

10) 6.1.1

11) All non-obsoleted releases

12) All releases b) Back to previous menu

Select the patch release to download, 'All non-obsoleted releases' to download all non-obsoleted releases, or 'All releases' to download all releases [1-5,b,q] 3

8 Select the number corresponding to the release that you want to download.

You can download a single release, all non-obsoleted releases, or all releases.

The selected release images are downloaded to the Deployment Server.

Downloading sfha-rhel6_x86_64-6.0RP1 from SORT - https://sort.symantec.com

Downloading 215118373 bytes (Total 215118373 bytes [205.15 MB]): 100%

Untarring sfha-rhel6_x86_64-6.0RP1 ........................................... Done sfha-rhel6_x86_64-6.0RP1 has been downloaded successfully.

9 From the menu, select option 2, View/Remove Repository Images, and follow the prompts to check that the release images are loaded.

See

“Viewing or downloading available release images”

on page 87.

Performing centralized installations using the Deployment Server

Viewing or removing repository images stored in your repository

92

Viewing or removing repository images stored in your repository

You can use the Deployment Server to conveniently view or remove the release images that are stored in your repository.

To view or remove release images stored in your repository

1 Launch the Deployment Server.

# /opt/VRTS/install/deploy_sfha

You see the following output:

Task Menu:

R) Manage Repository Images

V) Version Check Systems

I) Install/Upgrade Systems

B) Define/Modify Install Bundles

T) Create Install Templates

Enter a Task: [R,M,V,S,I,U,B,?,T,Q]

2 Select option R, Manage Repository Images.

You see the following output:

1) View/Download Available Releases

2) View/Remove Repository Images

3) Load a Release Image b) Back to previous menu

M) Update Metadata

S) Set Preferences

U) Terminology and Usage

?) Help

Q) Quit

Select the option you would like to perform [1-3,b,q,?]

Performing centralized installations using the Deployment Server

Viewing or removing repository images stored in your repository

93

3 Select option 2, View/Remove Repository Images, to view or remove the release images currently installed on your system.

You see a list of platforms and release levels if you have downloaded the corresponding Base, Maintenance, or Patch release on that platform.

To view or remove repository images, the platform type and release level type must be selected.

1) AIX 5.3

3) AIX 7.1

5) RHEL5 x86_64

7) RHEL7 x86_64

9) SLES11 x86_64

11) Solaris 10 Sparc

13) Solaris 11 Sparc b) Back to previous menu

2)

4)

6)

8)

AIX 6.1

HP-UX 11.31

RHEL6 x86_64

SLES10 x86_64

10) Solaris 9 Sparc

12) Solaris 10 x64

14) Solaris 11 x64

Select the platform of the release to view/remove [1-14,b,q]

4 Select the release level for which you want to get release image information.

Enter the platform you want.

You see options for the Symantec release levels if you have downloaded the corresponding Base, Maintenance, or Patch release.

1) Base

2) Maintenance

3) Patch b) Back to previous menu

Select the level of the <platform> releases to view/remove

[1-3,b,q]

5 Select the number corresponding to the type of release you want to view or remove (Base, Maintenance, or Patch).

You see a list of releases that are stored in your repository.

Stored Repository Releases: release_version SORT_release_name OBS AI

================================================

6.0RP1

6.0.3

sfha-rhel6_x86_64-6.0RP1

sfha-rhel6_x86_64-6.0.3

-

-

Y

Y

Performing centralized installations using the Deployment Server

Deploying Symantec product updates to your environment

94

6 If you are interested in viewing more details about a release image that is stored in your repository, type the release version. For example, enter the following:

6.0.3

7 If you do not need to check detail information, you can press Enter.

You see the following question:

Would you like to remove a rhel6_x86_64 Maintenance Release Image?

[y,n,q] (n) y

If you select a y, you see a menu of all the releases that are stored in your repository that match the selected platform and release level.

1) 6.0RP1

2) 6.0.3

b) Back to previous menu

Select the patch release to remove [1-2,b,q] 1

8 Type the number corresponding to the release version you want to remove.

The release images are removed from the Deployment Server.

Removing sfha-rhel6_x86_64-6.0RP1-patches ..................... Done sfha-rhel6_x86_64-6.0RP1-patches has been removed successfully.

Deploying Symantec product updates to your environment

You can use the Deployment Server to deploy release images to the systems in your environment as follows:

■ If you are not sure what to deploy, perform a version check. A version check tells you if there are any Symantec products installed on your systems. It suggests patches and maintenance releases, and gives you the option to install updates.

See

“Finding out which releases you have installed, and which upgrades or updates you may need”

on page 95.

Performing centralized installations using the Deployment Server

Finding out which releases you have installed, and which upgrades or updates you may need

95

■ If you know which update you want to deploy on your systems, use the

Install/Upgrade Systems script to deploy a specific Symantec release.

See

“Deploying Symantec releases”

on page 104.

Finding out which releases you have installed, and which upgrades or updates you may need

Use the Version Check option to determine which Symantec product you need to deploy. The Version Check option is useful if you are not sure which releases you already have installed, or you want to know about available releases.

The Version Check option gives you the following information:

Installed products and their versions (base, maintenance releases, and patches)

Installed RPMs (required and optional)

■ Available releases (base, maintenance releases, and patches) relative to the version which is installed on the system

To determine which Symantec product updates to deploy

1 Launch the Deployment Server. For example, enter the following:

# /opt/VRTS/install/deploy_sfha

You see the following output:

Task Menu:

R) Manage Repository Images

V) Version Check Systems

I) Install/Upgrade Systems

B) Define/Modify Install Bundles

T) Create Install Templates

Enter a Task: [R,M,V,S,I,U,B,?,T,Q]

2 Select option V, Version Check Systems.

M) Update Metadata

S) Set Preferences

U) Terminology and Usage

?) Help

Q) Quit

Performing centralized installations using the Deployment Server

Finding out which releases you have installed, and which upgrades or updates you may need

96

3 At the prompt, enter the system names for the systems you want to check. For example, enter the following: sys1

You see output for the installed RPMs (required, optional, or missing).

You see a list of releases available for download.

Available Base Releases for Veritas Storage Foundation HA 6.0.1: release_version SORT_release_name DL rel_date size_KB

==============================================================

6.0.2

6.1

sfha-rhel6_x86_64-6.0.2 sfha-rhel6_x86_64-6.1

Y

2012-10-22 985909

2013-12-02 1047939

Available Maintenance Releases for Veritas Storage Foundation HA 6.0.1: release_version SORT_release_name DL OBS AI rel_date size_KB

=====================================================================

6.0.3

6.0.5

6.1.1

sfha-rhel6_x86_64-6.0.3 sfha-rhel6_x86_64-6.0.5 Y sfha-rhel6_x86_64-6.1.1 -

Y

-

-

-

-

-

2013-02-01 212845

2014-04-15 199143

2014-07-24 208028

Available Patches for Veritas Storage Foundation HA 6.0.1: release_version SORT_release_name DL OBS AI rel_date size_KB

========================================================================

6.0.1.200-vm

6.0.1.300-fs vm-rhel6_x86_64-6.0.1.200

fs-rhel6_x86_64-6.0.1.300a -

Y

Y

-

-

2012-10-10 21359

2012-12-20 7601

Would you like to download the available Maintenance or Patch releases that cannot be found in the repository? [y,n,q] (n)

4 If you want to download any of the available maintenance releases or patches, enter y.

5 If you have not set a default repository for releases you download, the installer prompts you for a directory. (You can also set the default repository in Set

Preferences).

See

“Setting deployment preferences”

on page 83.

6 Select an option for downloading products.

The installer downloads the releases you specified and stores them in the repository.

Performing centralized installations using the Deployment Server

Defining Install Bundles

97

Defining Install Bundles

You can use Install Bundles to directly install the latest base, maintenance, and patch releases on your system. Install Bundles are a combination of base, maintenance, and patch releases that can be bundled and installed or upgraded in one operation.

Note: Install Bundles can be defined only from version 6.1 or later. The exception to this rule is base releases 6.0.1, 6.0.2, or 6.0.4 or later with maintenance release

6.0.5 or later.

To define Install Bundles

1 Launch the Deployment Server.

# /opt/VRTS/install/deploy_sfha

You see the following output:

Task Menu:

R) Manage Repository Images

V) Version Check Systems

I) Install/Upgrade Systems

B) Define/Modify Install Bundles

T) Create Install Templates

Enter a Task: [R,M,V,S,I,U,B,?,T,Q]

M) Update Metadata

S) Set Preferences

U) Terminology and Usage

?) Help

Q) Quit

2 Select option B, Define/Modify Install Bundles.

You see the following output the first time you enter:

Select a Task:

1) Create a new Install Bundle b) Back to previous menu

Select the task you would like to perform [1-1,b,q]

Performing centralized installations using the Deployment Server

Defining Install Bundles

98

3 Select option 1, Create a new Install Bundle.

You see the following output:

Enter the name of the Install Bundle you would like to define:

{press [Enter] to go back)

For example, if you entered: rhel605

You see the following output:

To create an Install Bundle, the platform type must be selected:

1) AIX 5.3

3) AIX 7.1

5) RHEL5 x86_64

7) RHEL7 x86_64

9) SLES11 x86_64

11) Solaris 10 Sparc

13) Solaris 11 Sparc b) Back to previous menu

2) AIX 6.1

4) HP-UX 11.31

6) RHEL6 x86_64

8) SLES10 x86_64

10) Solaris 9 Sparc

12) Solaris 10 x64

14) Solaris 11 x64

Select the platform of the release for the Install Bundle rhel605:

[1-14,b,q]

Performing centralized installations using the Deployment Server

Defining Install Bundles

99

4 Select the number corresponding to the platform you want to include in the

Install Bundle. For example, select the number for the RHEL5 x86_64 release,

5.

You see the following output:

Details of the Install Bundle: rhel605

Install Bundle Name

Platform

Base Release

Maintenance Release

Patch Releases rhel605

RHEL5 x86_64

N/A

N/A

N/A

1) Add a Base Release

2) Add a Maintenance Release

3) Add a Patch Release

4) Change Install Bundle Name b) Back to previous menu

Select an action to perform on the Install Bundle rhel605 [1-4,b,q]

5 Select option 1, Add a Base Release.

You see the following output:

1) 6.0.1

2) 6.0.2

3) 6.1

b) Back to previous menu

Select the Base Release version to add to the Install Bundle rhel605

[1-3,b,q]

Performing centralized installations using the Deployment Server

Defining Install Bundles

100

6 Select option 1, 6.0.1.

You see the following output:

Symantec Storage Foundation and High Availability Solutions 6.2 Deployment Server Program pilotlnx11

Details of the Install Bundle: rhel605

Install Bundle Name

Platform

Base Release

Maintenance Release

Patch Releases rhel605

RHEL5 x86_64

6.0.1

N/A

N/A

1) Remove Base Release 6.0.1

2) Add a Maintenance Release

3) Add a Patch Release

4) Change Install Bundle Name b) Back to previous menu

Select an action to perform on the Install Bundle rhel605 [1-4,b,q]

7 Select option 2, Add a Maintenance Release.

You see the following output:

1) 6.0.5

b) Back to previous menu

Select the Maintenance Release version to add to the Install Bundle rhel605 [1-1,b,q]

Performing centralized installations using the Deployment Server

Defining Install Bundles

101

8 Select option 1, 6.0.5.

You see the following output:

Symantec Storage Foundation and High Availability Solutions 6.2 Deployment Server Program pilotlnx11

Details of the Install Bundle: rhel605

Install Bundle Name

Platform

Base Release

Maintenance Release

Patch Releases rhel605

RHEL5 x86_64

6.0.1

6.0.5

N/A

1) Remove Base Release 6.0.1

2) Remove Maintenance Release 6.0.5

3) Add a Patch Release

4) Save Install Bundle rhel605

5) Change Install Bundle Name b) Back to previous menu

Select an action to perform on the Install Bundle rhel605

[1-5,b,q]

9 Select option 4, Save Install Bundle.

You see the following output:

Install Bundle rhel605 has been saved successfully

Press [Enter] to continue:

If there are no releases for the option you selected, you see a prompt saying that there are no releases at this time. You are prompted to continue.

After selecting the desired base, maintenance, or patch releases, you can choose to save your Install Bundle.

The specified Install Bundle is saved on your system. The specified Install

Bundle is available as an installation option when using the I) Install/Upgrade

Systems option to perform an installation or upgrade.

Performing centralized installations using the Deployment Server

Creating Install Templates

102

Creating Install Templates

You can use Install Templates to discover installed components (RPMs, patches, products, or versions) on a system that you want to replicate. Use Install Templates to automatically install those same components on to other systems.

To create Install Templates

1 Launch the Deployment Server.

# /opt/VRTS/install/deploy_sfha

2 You see the following output:

Task Menu:

R) Manage Repository Images

V) Version Check Systems

I) Install/Upgrade Systems

B) Define/Modify Install Bundles

T) Create Install Templates

Enter a Task: [R,M,V,S,I,U,B,?,T,Q]

M) Update Metadata

S) Set Preferences

U) Terminology and Usage

?) Help

Q) Quit

3 Select option T, Create Install Templates.

4 You see the following output:

Select a Task:

1) Create a new Install Template b) Back to previous menu

Select the task you would like to perform [1-1,b,q]

Performing centralized installations using the Deployment Server

Creating Install Templates

103

5 Select option 1, Create a new Install Template.

You see the following output:

Enter the system names separated by spaces for creating an Install Template:

(press [Enter] to go back)

For example, if you entered rhel89202 as the system name, you see the following output:

Enter the system names separated by spaces for version checking: rhel89202

Checking communication on rhel89202 .............................................. Done

Checking installed products on rhel89202 ......................................... Done

Platform of rhel89202:

Linux RHEL 6.3 x86_64

Installed product(s) on rhel89202:

Symantec Storage Foundation Cluster File System HA - 6.1.1 - license vxkeyless

Product:

Symantec Storage Foundation Cluster File System HA - 6.1.1 - license vxkeyless

Packages:

Installed Required packages for Symantec Storage Foundation Cluster File System HA 6.1.1:

#PACKAGE

VRTSamf

#VERSION

6.1.1.000

VRTSaslapm 6.1.1.000

..........

.........

..........

.........

VRTSvxfs 6.1.1.000

VRTSvxvm 6.1.1.000

Installed optional packages for Symantec Storage Foundation Cluster File System HA 6.1.1:

#PACKAGE #VERSION

VRTSdbed

VRTSgms

6.1.1.000

6.1.0.000

..........

.........

..........

.........

VRTSvcsdr

VRTSvcsea

6.1.0.000

6.1.1.000

Missing optional packages for Symantec Storage Foundation Cluster File System HA 6.1.1:

#PACKAGE

Performing centralized installations using the Deployment Server

Deploying Symantec releases

104

VRTScps

VRTSfssdk

VRTSlvmconv

Summary:

Packages:

17 of 17 required Symantec Storage Foundation Cluster File System HA 6.1.1 packages installed

8 of 11 optional Symantec Storage Foundation Cluster File System HA 6.1.1 packages installed

Installed Public and Private Hot Fixes for Symantec Storage Foundation Cluster File

System HA 6.1.1:

None

Would you like to generate a template file based on the above release information? [y,n,q] (y)

1) rhel89202 b) Back to previous menu

Select a machine list to generate the template file [1-1,b,q]

6 Select option 1, rhel89202.

You see the following output:

Enter the name of the Install Template you would like to define:

(press [Enter] to go back)

7 Enter the name of your Install Template. For example, if you enter MyTemplate as the name for your Install Template, you would see the following:

Install Template MyTemplate has been saved successfully

Press [Enter] to continue:

All of the necessary information is stored in the Install Template you created.

Deploying Symantec releases

You can use the Deployment Server to deploy your licensed Symantec products dating back to version 5.1. If you know which product version you want to install, follow the steps in this section to install it.

You can use the Deployment Server to install the following:

Performing centralized installations using the Deployment Server

Deploying Symantec releases

105

A single Symantec release

Two or more releases using defined Install Bundles

See

“Defining Install Bundles”

on page 97.

Installed components on a system that you want to replicate on another system

See

“Creating Install Templates”

on page 102.

To deploy a specific Symantec release

1 From the directory in which you installed your Symantec product (version 6.1

or later), launch the Deployment Server with the upgrade and install systems option. For example, enter the following:

# /opt/VRTS/install/deploy_sfha

You see the following output:

Task Menu:

R) Manage Repository Images

V) Version Check Systems

I) Install/Upgrade Systems

B) Define/Modify Install Bundles

T) Create Install Templates

Enter a Task: [R,M,V,S,I,U,B,?,T,Q]

M) Update Metadata

S) Set Preferences

U) Terminology and Usage

?) Help

Q) Quit

2 Select option I, Install/Upgrade Systems.

You see the following output:

1) AIX 5.3

2) AIX 6.1

3) AIX 7.1

4) RHEL5 x86_64 b) Back to previous menu

Select the platform of the available release(s) to be upgraded/installed [1-4,b,q,?]

Performing centralized installations using the Deployment Server

Deploying Symantec releases

106

3 Select the number corresponding to the platform for the release you want to deploy. For example, select the number for the RHEL5 x86_64 release or the

AIX 6.1 release.

You see the following output:

1) Install/Upgrade systems using a single release

2) Install/Upgrade systems using an Install Bundle

3) Install systems using an Install Template b) Back to previous menu

Select the method by which you want to Install/Upgrade your systems

[1-3,b,q]

4 Section option 1, Install/Upgrade systems using a single release if you want to deploy a specific Symantec release.

Select a Symantec product release.

The installation script is executed and the release is deployed on the specified server.

To deploy an Install Bundle

1 Follow Steps

1

-

3 .

2 Select option 2, Install/Upgrade systems using an Install Bundle.

You see the following output:

1) <NameofInstallBundle1>

2) <NameofInstallBundle2> b) Back to previous menu

Select the bundle to be installed/upgraded [1-2,b,q]

You see the following output:

Enter the platform target system name(s) separated by spaces:

[press [Enter] to go back)

3 Enter the name of the target system for which you want to install or upgrade the Install Bundle.

The installation script for the selected Install Bundle is executed, and the Install

Bundle is deployed on the specified target system.

Performing centralized installations using the Deployment Server

Connecting the Deployment Server to SORT using a proxy server

107

To deploy an Install Template

1 Follow Steps

1

-

3 .

2 Select option 3, Install/Upgrade systems using an Install Template.

You see the following output:

1) <NameofInstallTemplate> b) Back to previous menu

Select the template to be installed [1-1,b,q] 1

You see the following output:

Enter the platform target system name(s) separated by spaces:

[press [Enter] to go back)

The installation script for the selected Install Template is executed, and the

Install Template is deployed on the specified target system.

Connecting the Deployment Server to SORT using a proxy server

You can use a proxy server, a server that acts as an intermediary for requests from clients, for connecting the Deployment Server to the Symantec Operations

Readiness Tools (SORT) website.

To enable the proxy access, run the following commands to set the shell environment variables before you launch Deployment Server. The shell environment variables enable Deployment Server to use the proxy server myproxy.mydomain.com

which connects to port 3128.

http_proxy="http://myproxy.mydomain.com:3128" export http_proxy ftp_proxy="http://myproxy.mydomain.com:3128" export ftp_proxy

The lines above can be added to the user's shell profile. For the bash shell, the profile is the ~/.bash_profile

file.

Section

4

Upgrade of SF

Chapter 12. Planning to upgrade SF

Chapter 13. Upgrading Storage Foundation

Chapter 14. Performing an automated SF upgrade using response files

Chapter 15. Migrating from Storage Foundation Basic to Storage Foundation

Standard

Chapter 16. Performing post-upgrade tasks

Chapter

12

Planning to upgrade SF

This chapter includes the following topics:

Upgrade methods for SF

Supported upgrade paths for SF 6.2

About using the installer to upgrade when the root disk is encapsulated

Preparing to upgrade SF

Using Install Bundles to simultaneously install or upgrade full releases (base, maintenance, rolling patch), and individual patches

Upgrade methods for SF

Symantec offers you several different ways to upgrade. You need to decide which upgrade method best suits your environment, your expertise, and the downtime required.

Table 12-1 Review this table to determine how you want to perform the upgrade

Upgrade types and considerations Methods available for upgrade

Typical upgrades—use a Symantec provided tool or you can perform the upgrade manually.

Requires some server downtime.

Script-based—you can use this method to upgrade for the supported upgrade paths

Web-based—you can use this method to upgrade for the supported upgrade paths

Response file—you can use this method to upgrade from the supported upgrade paths

Upgrade from any supported UNIX or Linux platform to any other supported UNIX or Linux platform.

Deployment Server

See

“About the Deployment Server”

on page 77.

Planning to upgrade SF

Supported upgrade paths for SF 6.2

110

Table 12-1 Review this table to determine how you want to perform the upgrade

(continued)

Upgrade types and considerations

Simultaneously upgrade base releases, maintenance patches, and patches.

Methods available for upgrade

Install Bundles

See

“Using Install Bundles to simultaneously install or upgrade full releases (base, maintenance, rolling patch), and individual patches”

on page 120.

Supported upgrade paths for SF 6.2

The following tables describe upgrading to 6.2.

See

“Enabling DMP support for native devices”

on page 152.

Table 12-2 RHEL6 x64 upgrades using the script- or web-based installer

Symantec product versions

5.1

5.1 RPs

5.1 SP1RP1

RHEL5 RHEL 6

5.1 SP1 PR2

No upgrade path exists.

Uninstall the product.

Upgrade the operating system to one of the supported Linux versions, and then use the installer script to install 6.2. See the Storage

Foundation Release Notes for the supported Linux versions.

N/A

N/A Upgrade the operating system to one of the supported Linux versions, and then use the installer script to upgrade to 6.2. See the

Storage Foundation Release

Notes for the supported Linux versions.

Planning to upgrade SF

Supported upgrade paths for SF 6.2

111

Table 12-2

Symantec product versions

5.1 SP1 PR3

5.1 SP1 RP2

5.1 SP1 RP3

5.1 SP1 RP4

6.0

6.0 RPs

6.0.1

6.0.2

6.0.3

6.0.5

6.1

6.1.1

RHEL6 x64 upgrades using the script- or web-based installer

(continued)

RHEL5 RHEL 6

No upgrade path exists.

Uninstall the product.

Upgrade the operating system to one of the supported Linux versions, and then use the installer script to install 6.2. See the Storage

Foundation Release Notes for the supported Linux versions.

Upgrade the operating system to one of the supported Linux versions, and then use the installer script to upgrade to 6.2. See the

Storage Foundation Release

Notes for the supported Linux versions.

No upgrade path exists.

Uninstall the product.

Upgrade the operating system to one of the supported Linux versions, and then use the installer script to install 6.2. See the Storage

Foundation Release Notes for the supported Linux versions.

Upgrade the operating system to one of the supported Linux versions, and then use the installer script to upgrade to 6.2. See the

Storage Foundation Release

Notes for the supported Linux versions.

No upgrade path exists.

Uninstall the product.

Upgrade the operating system to one of the supported Linux versions, and then use the installer script to install 6.2. See the Storage

Foundation Release Notes for the supported Linux versions.

Use the installer to upgrade your Symantec product to 6.2.

Note: Symantec does not support the RHEL5 operating system with SFHA 6.2.

Planning to upgrade SF

Supported upgrade paths for SF 6.2

112

Table 12-3

6.0

6.0 RPx

6.0.1

6.0.2

6.0.3

6.0.5

SLES 11 x86-x64 upgrades using the script- or web-based installer

Symantec product versions

5.1

5.1 RPx

5.1 SP1

5.1 SP1 RPx

SLES 10 SLES 11

No upgrade path exists.

Uninstall the product.

Upgrade the operating system to one of the supported Linux versions, and then use the installer script to install 6.2. See the

Storage Foundation

Release Notes for the supported Linux versions.

Upgrade the operating system to one of the supported Linux versions, and then use the installer script to upgrade to 6.2. See the

Storage Foundation Release

Notes for the supported Linux versions.

No upgrade path exists.

Uninstall the product.

Upgrade the operating system to one of the supported Linux versions, and then use the installer script to install 6.2. See the

Storage Foundation

Release Notes for the supported Linux versions.

Upgrade the operating system to one of the supported Linux versions, and then use the installer script to upgrade to 6.2. See the

Storage Foundation Release

Notes for the supported Linux versions.

No upgrade path exists.

Uninstall the product.

Upgrade the operating system to one of the supported Linux versions, and then use the installer script to install 6.2. See the

Storage Foundation

Release Notes for the supported Linux versions.

Upgrade the operating system to one of the supported Linux versions, and then use the installer script to upgrade to 6.2. See the

Storage Foundation Release

Notes for the supported Linux versions.

N/A Use the installer to upgrade to 6.2.

6.0.4

6.1

6.1.1

Planning to upgrade SF

About using the installer to upgrade when the root disk is encapsulated

113

About using the installer to upgrade when the root disk is encapsulated

When you use the installer to upgrade from a previous version of SF and the system where you plan to upgrade has an encapsulated root disk, you may have to unecapsulate it.

Table 12-4 Upgrading using the installer when the root disk is encapsulated

(SUSE Linux Enterprise 11)

Starting version

5.1

5.1 RPx

5.1 SP1

5.1 SP1 RPx

6.0

6.0 RPx

6.0.1

6.0.3

6.0.4

6.0.5

6.1

6.1.1

Ending version

6.2

6.2

6.2

6.2

6.2

Action required

Do not unencapsulate. The installer runs normally.

Reboot after upgrade.

Do not unencapsulate. The installer runs normally.

Reboot after upgrade.

Do not unencapsulate. The installer runs normally.

Reboot after upgrade.

Do not unencapsulate. The installer runs normally.

Reboot after upgrade.

Do not unencapsulate. The installer runs normally.

Reboot after upgrade.

Table 12-5

Starting version

5.1 SP1 PR2

5.1 SP1 RP3

5.1 SP1 RP4

Upgrading using the installer when the root disk is encapsulated

(Red Hat Enterprise Linux 6)

Ending version

6.2

6.2

Action required

You need to unencapsulate the root disk. The installer exits.

Do not unencapsulate. The installer runs normally.

Reboot after upgrade.

Planning to upgrade SF

Preparing to upgrade SF

114

6.0.1

6.0.3

6.0.5

6.1

6.1.1

Table 12-5

Starting version

6.0

6.0 RPx

Upgrading using the installer when the root disk is encapsulated

(Red Hat Enterprise Linux 6) (continued)

Ending version

6.2

6.2

Action required

You need to unencapsulate the root disk. The installer exits.

Do not unencapsulate. The installer runs normally.

Reboot after upgrade.

Preparing to upgrade SF

Before you upgrade, you need to prepare the systems and storage. Review the following procedures and perform the appropriate tasks.

Getting ready for the upgrade

Complete the following tasks before you perform the upgrade:

■ Review the Symantec Storage Foundation Release Notes for any late-breaking information on upgrading your system.

Review the Symantec Technical Support website for additional information: http://www.symantec.com/techsupp/

Make sure that the administrator who performs the upgrade has root access and a good knowledge of the operating system's administration.

Make sure that all users are logged off and that all major user applications are properly shut down.

Make sure that you have created a valid backup.

See

“Creating backups”

on page 115.

Ensure that you have enough file system space to upgrade. Identify where you want to copy the RPMs, for example /packages/Veritas when the root file system has enough space or /var/tmp/packages if the /var file system has enough space.

Do not put the files under

/tmp

, which is erased during a system restart.

Planning to upgrade SF

Preparing to upgrade SF

115

Do not put the files on a file system that is inaccessible before running the upgrade script.

You can use a Symantec-supplied disc for the upgrade as long as modifications to the upgrade script are not required.

For any startup scripts in

/etc/init.d/

, comment out any application commands or processes that are known to hang if their file systems are not present.

Make sure that the current operating system supports version 6.2 of the product.

If the operating system does not support it, plan for a staged upgrade.

Schedule sufficient outage time and downtime for the upgrade and any applications that use the Symantec products. Depending on the configuration, the outage can take several hours.

Any swap partitions not in rootdg must be commented out of /etc/fstab . If possible, swap partitions other than those on the root disk should be commented out of /etc/fstab and not mounted during the upgrade. The active swap partitions that are not in rootdg cause upgrade_start to fail.

Make sure that the file systems are clean before upgrading.

Upgrade arrays (if required).

See

“Upgrading the array support”

on page 120.

To reliably save information on a mirrored disk, shut down the system and physically remove the mirrored disk. Removing the disk in this manner offers a failback point.

Determine if the root disk is encapsulated.

See

“Determining if the root disk is encapsulated”

on page 116.

If CP server-based coordination points are used in your current fencing configuration, then check that your CP servers are upgraded to 6.2 before starting the upgrade process.

Make sure that DMP support for native stack is disabled

( dmp_native_support=off ). If DMP support for native stack is enabled

( dmp_native_support=on ), the installer may detect it and ask you to restart the system.

Creating backups

Save relevant system information before the upgrade.

Planning to upgrade SF

Preparing to upgrade SF

116

To create backups

1 Log in as superuser.

2 Before the upgrade, ensure that you have made backups of all data that you want to preserve.

3 Back up information in files such as /boot/grub/menu.lst

, /etc/grub.conf

or /etc/lilo.conf

, and /etc/fstab .

4 Installer verifies that recent backups of configuration files in VxVM private region have been saved in

/etc/vx/cbr/bk

.

If not, a warning message is displayed.

Warning: Backup /etc/vx/cbr/bk directory.

5 Copy the fstab file to fstab.orig

:

# cp /etc/fstab /etc/fstab.orig

6 Run the vxlicrep

, vxdisk list

, and vxprint -ht commands and record the output. Use this information to reconfigure your system after the upgrade.

7 If you install the high availability version of the Symantec Storage Foundation

6.2 software, follow the guidelines that are given in the Symantec Cluster Server

Installation Guide and Symantec Cluster Server Release Notes for information on preserving your VCS configuration across the installation procedure.

8 Back up the external quotas and quotas.grp

files.

If you are upgrading from 6.0.3, you must also back up the quotas.grp.64

and quotas.64

files.

9 If you are planning on performing a Phased or Rolling upgrade from 6.0.3 and use quotas, you need to disable them:

# vxquotaoff -av

10 Verify that quotas are turned off on all the mounted file systems.

Determining if the root disk is encapsulated

Check if the system’s root disk is under VxVM control by running this command:

# df -v /

Planning to upgrade SF

Preparing to upgrade SF

117

The root disk is under VxVM control if

/dev/vx/dsk/rootdg/rootvol is listed as being mounted as the root (

/

) file system.

If the root disk is encapsulated, follow the appropriate upgrade procedures.

See

“About using the installer to upgrade when the root disk is encapsulated”

on page 113.

Pre-upgrade tasks for migrating the SFDB repository database

If you plan to continue using Database Storage Checkpoints or SmartTier for Oracle policies you created with a 5.0x or earlier version of Storage Foundation for Oracle, you must prepare to migrate the SFDB repository database to 6.2 before upgrading to Storage Foundation or Storage Foundation for Oracle RAC 6.2.

Note: The Sfua_Base repository resource group will be removed from the main.cf

file. It is not required as a separate service group for SF 6.2.

Perform the following before upgrading SF.

To prepare to migrate the repository database

◆ Resynchronize all existing snapshots before upgrading. As Oracle user, enter:

$ /opt/VRTS/bin/dbed_vmsnap -S $ORACLE_SID \

-f SNAPPLAN -o resync

Warning: The Database Flashsnap clone database will not be able to be carried over after upgrading. You must create a new Database Flashsnap clone database after upgrading to 6.2.

Pre-upgrade planning for Volume Replicator

Before installing or upgrading Volume Replicator (VVR):

■ Confirm that your system has enough free disk space to install VVR.

Make sure you have root permissions. You must have root permissions to perform the install and upgrade procedures.

If replication using VVR is configured, Symantec recommends that the disk group version is at least 110 prior to upgrading.

You can check the Disk Group version using the following command:

# vxdg list diskgroup

Planning to upgrade SF

Preparing to upgrade SF

118

If replication using VVR is configured, make sure the size of the SRL volume is greater than 110 MB.

Refer to the Symantec Storage Foundation and High Availability Solutions

Replication Administrator’s Guide.

If replication using VVR is configured, verify that all the Primary RLINKs are up-to-date on all the hosts.

# /usr/sbin/vxrlink -g diskgroup status rlink_name

Note: Do not continue until the primary RLINKs are up-to-date.

If VCS is used to manage VVR replication, follow the preparation steps to upgrade VVR and VCS agents.

See the Symantec Storage Foundation and High Availability Solutions Replication

Administrator's Guide for more information.

See the Getting Started Guide for more information on the documentation.

Planning an upgrade from the previous VVR version

If you plan to upgrade VVR from the previous VVR version, you can upgrade VVR with reduced application downtime by upgrading the hosts at separate times. While the Primary is being upgraded, the application can be migrated to the Secondary, thus reducing downtime. The replication between the (upgraded) Primary and the

Secondary, which have different versions of VVR, will still continue. This feature facilitates high availability even when the VVR upgrade is not complete on both the sites. Symantec recommends that the Secondary hosts be upgraded before the

Primary host in the Replicated Data Set (RDS).

See the Symantec Storage Foundation Release Notes for information regarding

VVR support for replicating across Storage Foundation versions.

Replicating between versions is intended to remove the restriction of upgrading the

Primary and Secondary at the same time. VVR can continue to replicate an existing

RDS with Replicated Volume Groups (RVGs) on the systems that you want to upgrade. When the Primary and Secondary are at different versions, VVR does not support changing the configuration with the vradmin command or creating a new

RDS.

Also, if you specify TCP as the network protocol, the VVR versions on the Primary and Secondary determine whether the checksum is calculated. As shown in

Table 12-6 , if either the Primary or Secondary are running a version of VVR prior

to 6.2, and you use the TCP protocol, VVR calculates the checksum for every data

Planning to upgrade SF

Preparing to upgrade SF

119 packet it replicates. If the Primary and Secondary are at VVR 6.2, VVR does not calculate the checksum. Instead, it relies on the TCP checksum mechanism.

Table 12-6 VVR versions and checksum calculations

VVR prior to 6.2

(DG version <= 140)

Primary

Secondary

Primary and Secondary

VVR 6.2

(DG version >= 150)

Secondary

Primary

Primary and Secondary

VVR calculates checksum

TCP connections?

Yes

Yes

Yes

No

Note: When replicating between versions of VVR, avoid using commands associated with new features. The earlier version may not support new features and problems could occur.

If you do not need to upgrade all the hosts in the RDS simultaneously, you can use replication between versions after you upgrade one host. You can then upgrade the other hosts in the RDS later at your convenience.

Note: If you have a cluster setup, you must upgrade all the nodes in the cluster at the same time.

Planning and upgrading VVR to use IPv6 as connection protocol

Storage Foundation supports using IPv6 as the connection protocol.

This release supports the following configurations for VVR:

■ VVR continues to support replication between IPv4-only nodes with IPv4 as the internet protocol

VVR supports replication between IPv4-only nodes and IPv4/IPv6 dual-stack nodes with IPv4 as the internet protocol

VVR supports replication between IPv6-only nodes and IPv4/IPv6 dual-stack nodes with IPv6 as the internet protocol

VVR supports replication between IPv6 only nodes

VVR supports replication to one or more IPv6 only nodes and one or more IPv4 only nodes from a IPv4/IPv6 dual-stack node

Planning to upgrade SF

Using Install Bundles to simultaneously install or upgrade full releases (base, maintenance, rolling patch), and individual patches

120

■ VVR supports replication of a shared disk group only when all the nodes in the cluster that share the disk group are at IPv4 or IPv6

Upgrading the array support

The Storage Foundation 6.2 release includes all array support in a single RPM,

VRTSaslapm

. The array support RPM includes the array support previously included in the

VRTSvxvm

RPM. The array support RPM also includes support previously packaged as external Array Support Libraries (ASLs) and array policy modules

(APMs).

See the 6.2 Hardware Compatibility List for information about supported arrays.

When you upgrade Storage Foundation products with the product installer, the installer automatically upgrades the array support. If you upgrade Storage

Foundation products with manual steps, you should remove any external ASLs or

APMs that were installed previously on your system. Installing the

VRTSvxvm

RPM exits with an error if external ASLs or APMs are detected.

After you have installed Storage Foundation 6.2, Symantec provides support for new disk arrays through updates to the VRTSaslapm RPM.

For more information about array support, see the Symantec Storage Foundation

Administrator's Guide.

Using Install Bundles to simultaneously install or upgrade full releases (base, maintenance, rolling patch), and individual patches

Beginning with version 6.1, Symantec offers you a method to easily install or upgrade your systems directly to a base, maintenance, patch level or a combination of multiple patches and packages together in one step using Install Bundles. With

Install Bundles, the installer has the ability to merge so that customers can install or upgrade directly to maintenance or patch levels in one execution. The various scripts, RPMs, and patch components are merged, and multiple releases are installed together as if they are one combined release. You do not have to perform two or more install actions to install or upgrade systems to maintenance levels or patch levels.

Releases are divided into the following categories:

Planning to upgrade SF

Using Install Bundles to simultaneously install or upgrade full releases (base, maintenance, rolling patch), and individual patches

121

Table 12-7

Level

Base

Patch

Release Levels

Content

Features

Maintenance Fixes, new features

Fixes

Form factor

RPMs

Applies to

All products

Release types

Download location

Major, minor,

Service Pack

(SP), Platform

Release (PR)

FileConnect

RPMs

RPMs

All products

Single product

Maintenance

Release

(MR), Rolling

Patch (RP)

Symantec

Operations

Readiness

Tools (SORT)

P-Patch,

Private Patch,

Public patch

SORT,

Support site

When you install or upgrade using Install Bundles:

SFHA products are discovered and assigned as a single version to the maintenance level. Each system can also have one or more patches applied.

Base releases are accessible from FileConnect that requires customer serial numbers. Maintenance and patch releases can be automatically downloaded from SORT. You can download them from the SORT website manually or use the deploy_sfha script.

Patches can be installed using automated installers from the 6.0.1 version or later.

Patches can now be detected to prevent upgrade conflict. Patch releases are not offered as a combined release. They are only available from Symantec

Technical Support on a need basis.

You can use the -base_path and -patch_path options to import installation code from multiple releases. You can find RPMs and patches from different media paths, and merge RPM and patch definitions for multiple releases. You can use these options to use new task and phase functionality to correctly perform required operations for each release component. You can install the RPMs and patches in defined phases using these options, which helps you when you want to perform a single start or stop process and perform pre and post operations for all level in a single operation.

Four possible methods of integration exist. All commands must be executed from the highest base or maintenance level install script.

For example:

Planning to upgrade SF

Using Install Bundles to simultaneously install or upgrade full releases (base, maintenance, rolling patch), and individual patches

122

1.

Base + maintenance:

This integration method can be used when you install or upgrade from a lower version to 6.2.1.

Enter the following command:

# installmr -base_path <path_to_base>

2.

Base + patch:

This integration method can be used when you install or upgrade from a lower version to 6.2.0.100.

Enter the following command:

# installer -patch_path <path_to_patch>

3.

Maintenance + patch:

This integration method can be used when you upgrade from version 6.2 to

6.2.1.100.

Enter the following command:

# installmr -patch_path <path_to_patch>

4.

Base + maintenance + patch:

This integration method can be used when you install or upgrade from a lower version to 6.2.1.100.

Enter the following command:

# installmr -base_path <path_to_base>

-patch_path <path_to_patch>

Note: From the 6.1 or later release, you can add a maximum of five patches using -patch_path <path_to_patch> -patch2_path <path_to_patch> ...

-patch5_path <path_to_patch>

Chapter

13

Upgrading Storage

Foundation

This chapter includes the following topics:

Upgrading Storage Foundation from previous versions to 6.2

Upgrading SF using the web-based installer

Upgrading Volume Replicator

Upgrading SFDB

Upgrading Storage Foundation from previous versions to 6.2

If you are running an earlier release of Storage Foundation, you can upgrade to the latest version using the procedures described in this chapter.

See

“Upgrading Storage Foundation using the script-based installer”

on page 123.

If you need to upgrade your kernel with Symantec Storage Foundation 6.2 already installed, use the kernel upgrade procedure.

See the Symantec Storage Foundation Administrator's Guide for information about upgrading the kernel.

Upgrading Storage Foundation using the script-based installer

Use this procedure to upgrade Storage Foundation (SF).

Upgrading Storage Foundation

Upgrading Storage Foundation from previous versions to 6.2

124

To upgrade SF from previous versions to 6.2

1 Log in as superuser.

2 Use the following command to check if any VxFS file systems or Storage

Checkpoints are mounted:

# df -F | grep vxfs

3 Unmount all Storage Checkpoints and file systems:

# umount /checkpoint_name

# umount /filesystem

4 Verify that all file systems have been cleanly unmounted:

# echo "8192B.p S" | fsdb -t vxfs filesystem | grep clean flags 0 mod 0 clean clean_value

A clean_value value of

0x5a indicates the file system is clean,

0x3c indicates the file system is dirty, and

0x69 indicates the file system is dusty. A dusty file system has pending extended operations.

Perform the following steps in the order listed:

■ If a file system is not clean, enter the following commands for that file system:

# fsck -t vxfs filesystem

# mount -t vxfs filesystem mountpoint

# umount mountpoint

This should complete any extended operations that were outstanding on the file system and unmount the file system cleanly.

There may be a pending large RPM clone removal extended operation if the umount command fails with the following error: file system device busy

You know for certain that an extended operation is pending if the following message is generated on the console:

Storage Checkpoint asynchronous operation on file_system file system still in progress.

■ If an extended operation is pending, you must leave the file system mounted for a longer time to allow the operation to complete. Removing a very large

RPM clone can take several hours.

Upgrading Storage Foundation

Upgrading Storage Foundation from previous versions to 6.2

125

■ Repeat this step to verify that the unclean file system is now clean.

5 If a cache area is online, you must take the cache area offline before you upgrade the VxVM RPM. Use the following command to take the cache area offline:

# sfcache offline cachename

6 Stop activity to all VxVM volumes. For example, stop any applications such as databases that access the volumes, and unmount any file systems that have been created on the volumes.

7 Stop all the volumes by entering the following command for each disk group:

# vxvol -g diskgroup stopall

To verify that no volumes remain open, use the following command:

# vxprint -Aht -e v_open

8 Make a record of the mount points for VxFS file systems and VxVM volumes that are defined in the /etc/fstab file. You will need to recreate these entries in the /etc/fstab file on the freshly installed system.

9 Perform any necessary preinstallation checks.

See

“About planning for SF installation”

on page 25.

10 To invoke the installer, run the installer command on the disc as shown in this example:

# cd /cdrom/cdrom0

# ./installer

11 Enter G to upgrade and press Return.

Upgrading Storage Foundation

Upgrading Storage Foundation from previous versions to 6.2

126

12 You are prompted to enter the system names (in the following example, "host1") on which the software is to be installed. Enter the system name or names and then press Return.

Enter the 64 bit <platform> system names separated by spaces : [q, ?] host1 host2 where <platform> is the platform on which the system runs, such as RHEL5.

Depending on your existing configuration, various messages and prompts may appear. Answer the prompts appropriately.

During the system verification phase, the installer checks if the boot disk is encapsulated and the upgrade's path. If the upgrade is not supported, you need to un-encapsulate the boot disk.

13 The installer asks if you agree with the terms of the End User License

Agreement. Press y to agree and continue.

14 The installler lists the RPMs to install or upgrade. You are prompted to confirm that you are ready to upgrade.

15 The installer discovers if any of the systems that you are upgrading have mirrored and encapsulated boot disks. For each system that has a mirrored boot disk, you have the option to create a backup of the system's book disk group before the upgrade proceeds. If you want to split the boot disk group to create a backup, answer y.

16 The installer then prompts you to name the backup boot disk group. Enter the name for it or press Enter to accept the default.

17 You are prompted to start the split operation. Press y to continue.

Note: The split operation can take some time to complete.

18 Stop the product's processes.

Do you want to stop SF processes now? [y,n,q] (y) y

If you select y

, the installer stops the product processes and makes some configuration updates before upgrading.

19 The installer stops, uninstalls, reinstalls, and starts specified RPMs.

20 If necessary, reinstate any missing mount points in the

/etc/fstab file on each node that you recorded in step

8 .

Upgrading Storage Foundation

Upgrading SF using the web-based installer

127

21 Restart all the volumes by entering the following command for each disk group:

# vxvol -g diskgroup startall

22 Remount all VxFS file systems and Storage Checkpoints on all nodes:

# mount /filesystem

# mount /checkpoint_name

23 You can perform the following optional configuration steps:

■ If you want to use features of Symantec Storage Foundation 6.2 for which you do not currently have an appropriate license installed, obtain the license and run the vxlicinst command to add it to your system.

■ To upgrade VxFS Disk Layout versions and VxVM Disk Group versions, follow the upgrade instructions.

See

“Upgrading VxVM disk group versions”

on page 149.

24 Only perform this step if you have split the mirrored root disk to back it up. After a successful reboot, verify the upgrade and re-join the backup disk group. If the upgrade fails, revert to the backup disk group.

See

“Re-joining the backup boot disk group into the current disk group”

on page 141.

See

“Reverting to the backup boot disk group after an unsuccessful upgrade”

on page 141.

Upgrading SF using the web-based installer

This section describes upgrading SF with the web-based installer. The installer detects and upgrades the product that is currently installed on the specified system or systems.

To upgrade SF

1 Perform the required steps to save any data that you want to preserve. For example, make configuration file backups.

2 Start the web-based installer.

See

“Starting the web-based installer”

on page 48.

3 On the Select a task and a product page, select Upgrade a Product from the

Task drop-down menu.

The product is discovered once you specify the system. Click Next.

Upgrading Storage Foundation

Upgrading SF using the web-based installer

128

4 Indicate the systems on which to upgrade. Enter one or more system names, separated by spaces. Click Next.

5 Installer detects the product that is installed on the specified system. It shows the cluster information and lets you confirm if you want to perform upgrade on the cluster. Select Yes and click Next.

6 On the License agreement page, select whether you accept the terms of the

End User License Agreement (EULA). To continue, select Yes I agree and click Next.

7 The installer discovers if any of the systems that you want to upgrade have mirrored and encapsulated boot disks. For each system that has a mirrored boot disk, you have the option to create a backup of the book disk group. To create the backup, check the Split mirrors on all the systems box. Check the appropriate box to use the same name for the backup disk group on all systems. You can use the default name or choose a new one. Check the systems where you want to create the backup. When you are ready, click the

Next button.

8 Click Next to complete the upgrade.

After the upgrade completes, the installer displays the location of the log and summary files. If required, view the files to confirm the installation status.

9 If you are prompted to restart the systems, enter the following restart command:

# /sbin/shutdown -r now

10 After the upgrade, if the product is not configured, the web-based installer asks:

"Do you want to configure this product?" If the product is already configured, it does not ask any questions.

11 Click Finish. The installer prompts you for another task.

12 Only perform this step if you have split the mirrored root disk to back it up. After a successful restart, verify the upgrade and re-join the backup disk group into the upgraded boot disk group. If the upgrade fails, revert the upgrade boot disk group to the backup disk group.

See

“Re-joining the backup boot disk group into the current disk group”

on page 141.

See

“Reverting to the backup boot disk group after an unsuccessful upgrade”

on page 141.

Upgrading Storage Foundation

Upgrading Volume Replicator

129

Upgrading Volume Replicator

If a previous version of Volume Replicator (VVR) is configured, the product installer upgrades VVR automatically when you upgrade the Storage Foundation products.

You have the option to upgrade without disrupting replication.

See

“Upgrading VVR without disrupting replication”

on page 129.

Upgrading VVR without disrupting replication

This section describes the upgrade procedure from an earlier version of VVR to the current version of VVR when replication is in progress, assuming that you do not need to upgrade all the hosts in the RDS simultaneously.

You may also need to set up replication between versions.

See

“Planning an upgrade from the previous VVR version”

on page 118.

When both the Primary and the Secondary have the previous version of VVR installed, the upgrade can be performed either on the Primary or on the Secondary.

We recommend that the Secondary hosts be upgraded before the Primary host in the RDS. This section includes separate sets of steps, for the Primary upgrade and for the Secondary upgrade.

Note: If you have a cluster setup, you must upgrade all the nodes in the cluster at the same time.

Upgrading VVR on the Secondary

Follow these instructions to upgrade the Secondary hosts.

To upgrade the Secondary

1 Stop replication to the Secondary host by initiating a Primary pause using the following command:

# vradmin -g diskgroup pauserep local_rvgname sec_hostname

2 Upgrade from VVR 5.1 or later to VVR 6.2 on the Secondary.

3 Do one of the following:

Upgrade the disk group now. Enter the following:

# vxdg upgrade dgname

Upgrade the disk group later.

Upgrading Storage Foundation

Upgrading SFDB

130

If you upgrade the disk group later, be sure to pause replication before you upgrade the disk group. Also, after pausing replication, upgrade the disk group on Primary as well as Secondary.

4 Resume the replication from the Primary using the following command:

# vradmin -g diskgroup resumerep local_rvgname sec_hostname

Upgrading VVR on the Primary

After you upgrade the Secondary, use the product installer to upgrade the Primary.

To upgrade the Primary

1 Stop replication to the Primary host by initiating a Primary pause using the following command:

# vradmin -g diskgroup pauserep local_rvgname

2 Upgrade from VVR 5.1 or later to VVR 6.2 on the Secondary.

3 Do one of the following:

■ Upgrade the disk group now. Enter the following:

# vxdg upgrade dgname

■ Upgrade the disk group later.

If you upgrade the disk group later, be sure to pause replication before you upgrade the disk group. Also, after pausing replication, upgrade the disk group on Primary as well as Secondary.

4 Resume the replication from the Primary using the following command:

# vradmin -g diskgroup resumerep local_rvgname sec_hostname

See

“Planning an upgrade from the previous VVR version”

on page 118.

Upgrading SFDB

While upgrading from 6.x to 6.2 the SFDB tools are enabled by default, which implies that the vxdbd daemon is configured. You can enable the SFDB tools, if they are disabled.

Upgrading Storage Foundation

Upgrading SFDB

131

To enable SFDB tools

1 Log in as root.

2 Run the following command to configure and start the vxdbd daemon.

# /opt/VRTS/bin/sfae_config enable

Note: If any SFDB installation with authentication setup is upgraded to 6.2, the commands fail with an error. To resolve the issue, setup the SFDB authentication again. For more information, see the Storage and Availability Management for

Oracle Databases or Storage and Availability Management for DB2 Databases.

Chapter

14

Performing an automated

SF upgrade using response files

This chapter includes the following topics:

Upgrading SF using response files

Response file variables to upgrade Storage Foundation

Sample response file for SF upgrade

Upgrading SF using response files

Typically, you can use the response file that the installer generates after you perform

SF upgrade on one system to upgrade SF on other systems.

You can also create a response file using the makeresponsefile option of the installer.

# ./installer -makeresponsefile

To perform automated SF upgrade

1 Make sure the systems where you want to upgrade SF meet the upgrade requirements.

2 Make sure the pre-upgrade tasks are completed.

3 Copy the response file to the system where you want to upgrade SF.

4 Edit the values of the response file variables as necessary.

Performing an automated SF upgrade using response files

Response file variables to upgrade Storage Foundation

133

5 Mount the product disc and navigate to the folder that contains the installation program.

6 Start the upgrade from the system to which you copied the response file. For example:

# ./installer -responsefile /tmp/response_file

# ./installsf -responsefile /tmp/response_file

Where /tmp/response_file is the response file’s full path name.

Response file variables to upgrade Storage

Foundation

Table 14-1

lists the response file variables that you can define to configure SF.

Table 14-1 Response file variables for upgrading SF

Variable

CFG{accepteula}

CFG{systems}

CFG{opt}{keyfile}

CFG{opt}{tmppath}

Description

Specifies whether you agree with the EULA.pdf file on the media.

List or scalar: scalar

Optional or required: required

List of systems on which the product is to be installed or uninstalled.

List or scalar: list

Optional or required: required

Defines the location of an ssh keyfile that is used to communicate with all remote systems.

List or scalar: scalar

Optional or required: optional

Defines the location where a working directory is created to store temporary files and the RPMs that are needed during the install. The default location is

/var/tmp.

List or scalar: scalar

Optional or required: optional

Performing an automated SF upgrade using response files

Response file variables to upgrade Storage Foundation

134

Table 14-1

Variable

CFG{opt}{logpath}

CFG{opt}{upgrade}

Response file variables for upgrading SF (continued)

Description

Mentions the location where the log files are to be copied. The default location is /opt/VRTS/install/logs.

List or scalar: scalar

Optional or required: optional

Upgrades all RPMs installed.

List or scalar: list

Optional or required: optional

CFG{mirrordgname}{system}

CFG{splitmirror}{system}

If the root dg is encapsulated and you select split mirror is selected:

Splits the target disk group name for a system.

List or scalar: scalar

Optional or required: optional

If the root dg is encapsulated and you select split mirror is selected:

Indicates the system where you want a split mirror backup disk group created.

List or scalar: scalar

Optional or required: optional

CFG{opt}{disable_dmp_native_support} If it is set to 1, Dynamic Multi-pathing support for the native LVM volume groups and ZFS pools is disabled after upgrade. Retaining Dynamic Multi-pathing support for the native LVM volume groups and ZFS pools during upgrade increases RPM upgrade time depending on the number of LUNs and native LVM volume groups and ZFS pools configured on the system.

List or scalar: scalar

Optional or required: optional

Performing an automated SF upgrade using response files

Sample response file for SF upgrade

135

Table 14-1 Response file variables for upgrading SF (continued)

Variable

CFG{opt}{patch_path}

CFG{opt}{patch2_path}

Description

Defines the path of a patch level release to be integrated with a base or a maintenance level release in order for multiple releases to be simultaneously installed .

List or scalar: scalar

Optional or required: optional

Defines the path of a second patch level release to be integrated with a base or a maintenance level release in order for multiple releases to be simultaneously installed.

List or scalar: scalar

Optional or required: optional

CFG{opt}{patch3_path}

CFG{opt}{patch4_path}

CFG{opt}{patch5_path}

Defines the path of a third patch level release to be integrated with a base or a maintenance level release in order for multiple releases to be simultaneously installed.

List or scalar: scalar

Optional or required: optional

Defines the path of a fourth patch level release to be integrated with a base or a maintenance level release in order for multiple releases to be simultaneously installed.

List or scalar: scalar

Optional or required: optional

Defines the path of a fifth patch level release to be integrated with a base or a maintenance level release in order for multiple releases to be simultaneously installed.

List or scalar: scalar

Optional or required: optional

Sample response file for SF upgrade

The following example shows a response file for upgrading Storage Foundation.

Performing an automated SF upgrade using response files

Sample response file for SF upgrade

136 our %CFG;

$CFG{accepteula}=1;

$CFG{opt}{upgrade}=1;

$CFG{systems}=[ qw(sys1) ];

1;

Chapter

15

Migrating from Storage

Foundation Basic to Storage

Foundation Standard

This chapter includes the following topics:

Migrating from Storage Foundation Basic to Storage Foundation Standard

Migrating from Storage Foundation Basic to Storage

Foundation Standard

Use this procedure to migrate from Storage Foundation (SF) Basic to Storage

Foundation Standard.

To migrate from Storage Foundation Basic to Storage Foundation Standard

1 Log in as superuser on a system where you want to install Storage Foundation

Standard.

2 Use the following command to confirm that you are currently running Storage

Foundation Basic.

# /opt/VRTSvlic/bin/vxlicrep | grep Basic

You should see the following output:

Product Name = VERITAS Storage Foundation Basic

3 Mount the installation media for Storage Foundation Standard.

Migrating from Storage Foundation Basic to Storage Foundation Standard

Migrating from Storage Foundation Basic to Storage Foundation Standard

138

4 Run the installer command.

# ./installer

The installer will first execute a set of prechecks.

5 Make sure that the prechecks complete successfully. Make any changes that the installer recommends.

6 On the Installer Task menu, select Install a Product.

7 On the Product Selection menu, select Symantec Storage Foundation.

8 At the prompt, specify whether you accept the terms of the End User License

Agreement (EULA). Press y to agree and continue.

9 Select the RPM level to be installed.

From the menu, select the option that corresponds to Install Recommended.

10 You are prompted to enter the system names on which to install Storage

Foundation Standard.

11 The installer prompts with a warning that Storage Foundation is already installed, and asks for confirmation to continue. Press y to continue the installation.

12 The installer will identify two additional RPMs to be installed, VRTSodm and

VRTSdbed . Press Enter to continue.

13 After installing the RPMs in step

12 , the installer will prompt if additional licenses

need to be installed. Press y to continue.

You will be provided two options:

■ Enter a license key

■ Utilize Keyless licensing

14 If you chose to enter a license key, you should install the Storage Foundation

Standard license key.

15 If you chose to utilize a keyless license, you will be asked to choose the version of Storage Foundation (Standard or Enterprise). Choose Standard to install a

Storage Foundation Standard license.

The installer will go through the configuration and startup process.

Migrating from Storage Foundation Basic to Storage Foundation Standard

Migrating from Storage Foundation Basic to Storage Foundation Standard

139

16 Confirm if you want to send information about this installation to Symantec to help improve the installation in the future.

Would you like to send the information about this installation to Symantec to help improve installation in the future? [y,n,q,?] (y)

17 If desired, press y to view the summary file.

The migration is complete.

Chapter

16

Performing post-upgrade tasks

This chapter includes the following topics:

Optional configuration steps

Re-joining the backup boot disk group into the current disk group

Reverting to the backup boot disk group after an unsuccessful upgrade

Post upgrade tasks for migrating the SFDB repository database

Recovering VVR if automatic upgrade fails

Upgrading disk layout versions

Upgrading VxVM disk group versions

Updating variables

Setting the default disk group

Verifying the Storage Foundation upgrade

Optional configuration steps

After the upgrade is complete, additional tasks may need to be performed.

You can perform the following optional configuration steps:

If Volume Replicator (VVR) is configured, do the following steps in the order shown:

Reattach the RLINKs.

Associate the SRL.

Performing post-upgrade tasks

Re-joining the backup boot disk group into the current disk group

141

To encapsulate and mirror the boot disk, follow the procedures in the

"Administering Disks" chapter of the Symantec Storage Foundation

Administrator’s Guide.

To upgrade VxFS Disk Layout versions and VxVM Disk Group versions, follow the upgrade instructions.

See

“Upgrading VxVM disk group versions”

on page 149.

Re-joining the backup boot disk group into the current disk group

Perform this procedure to rejoin the backup boot disk if you split the mirrored boot disk during upgrade. After a successful upgrade and reboot, you no longer need to keep the boot disk group backup.

To re-join the backup boot disk group

◆ Re-join the backup_bootdg disk group to the boot disk group.

# /etc/vx/bin/vxrootadm -Y join backup_bootdg where the

-Y option indicates a silent operation, and backup_bootdg is the name of the backup boot disk group that you created during the upgrade.

Reverting to the backup boot disk group after an unsuccessful upgrade

Perform this procedure if your upgrade was unsuccessful and you split the mirrored boot disk to back it up during upgrade. You can revert to the backup that you created when you upgraded.

To revert the backup boot disk group after an unsuccessful upgrade

1 To determine the boot disk groups, look for the rootvol volume in the output of the vxprint command.

# vxprint

2 Use the vxdg command to find the boot disk group where you are currently booted.

# vxdg bootdg

Performing post-upgrade tasks

Post upgrade tasks for migrating the SFDB repository database

142

3 Boot the operating system from the backup boot disk group.

4 Join the original boot disk group to the backup disk group.

# /etc/vx/bin/vxrootadm -Y join original_bootdg where the

-Y option indicates a silent operation, and original_bootdg is the boot disk group that you no longer need.

Post upgrade tasks for migrating the SFDB repository database

Database Storage Checkpoints that have been created by using the SFDB tools before upgrade are visible using the vxsfadm CLI, and you can mount these

Database Storage Checkpoints and roll back to them, if required. However, creating clones by using migrated Database Storage Checkpoints is not supported.

If you want to continue using previously created FlashSnap snapplans to take snapshots, you must validate them by using the

-o validate option of the vxsfadm command.

To continue using the Database Storage Checkpoints or SmartTier for Oracle policies you created with a 5.0x or earlier version of Storage Foundation for Oracle, you must perform one of the following procedures after upgrading SF to 6.2:

■ Rename startup script after upgrading from 5.0x and before migrating the SFDB repository

See

“Migrating SFDB from 5.0x to 6.2”

on page 147.

Migrate from a 5.0x SFDB repository database to 6.2

See

“Migrating from a 5.0 repository database to 6.2”

on page 142.

Migrate from a 5.1 or 5.1SP1 repository database to 6.2

See

“Migrating from a 5.1 or higher repository database to 6.2”

on page 145.

Migrating from a 5.0 repository database to 6.2

To migrate from a 5.0 repository database to 6.2

1 Rename the startup script NO_S*vxdbms3 to S*vxdbms3.

See

“Migrating SFDB from 5.0x to 6.2”

on page 147.

2 As root, dump out the old Sybase ASA repository. If you are using SFHA or

SF Oracle RAC, you only need to do this on one node.

# /opt/VRTSdbed/migrate/sfua_rept_migrate

Performing post-upgrade tasks

Post upgrade tasks for migrating the SFDB repository database

143

3 On the same node that you ran sfua_rept_migrate run the following command as Oracle user. For each Oracle instance, migrate the old repository data to the SQLite repository.

$ /opt/VRTS/bin/dbed_update -S $ORACLE_SID -H $ORACLE_HOME

4 By default, the repository is created on the file system which contains the Oracle

SYSTEM tablespace. If you need an alternative repository path, first verify the following requirements:

■ Repository path has to be a directory writable by Oracle user.

■ The update commands will not be able to verify accessibility of the repository path and will fail if you have not set up the path correctly.

Create an alternate repository path.

$ /opt/VRTS/bin/dbed_update -S $ORACLE_SID -H $ORACLE_HOME -R \

Alternate_path

5 If you are using Database Flashsnap for off-host processing, and if you have a repository on the secondary host that you need to migrate: perform the previous steps on the secondary host.

Performing post-upgrade tasks

Post upgrade tasks for migrating the SFDB repository database

144

6 On the primary host, edit your snapplans to remove the

"SNAPSHOT_DG=SNAP_*" parameter and add

“SNAPSHOT_DG_PREFIX=SNAP_*". The parameter can be any PREFIX value and not necessarily "SNAP_*".

For example:

$ /usr/oracle> more SNAPPLAN1

SNAPSHOT_VERSION=5.0

PRIMARY_HOST=system1

SECONDARY_HOST=system1.example.com

PRIMARY_DG=system1_data

SNAPSHOT_DG=SNAP_system1_data

ORACLE_SID=HN1

ARCHIVELOG_DEST=/oracle/orahome/dbs/arch

SNAPSHOT_ARCHIVE_LOG=yes

SNAPSHOT_MODE=online

SNAPSHOT_PLAN_FOR=database

SNAPSHOT_PLEX_TAG=dbed_flashsnap

SNAPSHOT_VOL_PREFIX=SNAP_

ALLOW_REVERSE_RESYNC=no

SNAPSHOT_MIRROR=1

$ /usr/oracle> more SNAPPLAN1

SNAPSHOT_VERSION=5.0

PRIMARY_HOST=system1

SECONDARY_HOST=system1.example.com

PRIMARY_DG=judge_data

SNAPSHOT_DG_PREFIX=SNAP_system1_data

ORACLE_SID=HN1

ARCHIVELOG_DEST=/oracle/orahome/dbs/arch

SNAPSHOT_ARCHIVE_LOG=yes

SNAPSHOT_MODE=online

SNAPSHOT_PLAN_FOR=database

SNAPSHOT_PLEX_TAG=dbed_flashsnap

SNAPSHOT_VOL_PREFIX=SNAP_

ALLOW_REVERSE_RESYNC=no

SNAPSHOT_MIRROR=1

Performing post-upgrade tasks

Post upgrade tasks for migrating the SFDB repository database

145

7 On the primary host, revalidate your snapshots using the following command:

$ /opt/VRTS/bin/vxsfadm -s flashsnap \

-a oracle -c SNAPPLAN -o validate

This completes the migration of the repository for Database Storage

Checkpoints and Database Tiered Storage parameters.

Note: While you revalidate the snapshot configuration file ( snapplan

) from an older release, use the vxsfadm -c <configfile> option to avoid the default values from overriding the old values.

To begin using the Storage Foundation for Databases (SFDB) tools: see Storage Foundation: Storage and Availability Management for Oracle Databases.

Migrating from a 5.1 or higher repository database to 6.2

To migrate from a 5.1 or higher repository database to 6.2

1 Run the following command as Oracle user. For each Oracle instance, migrate the old repository data to the SQLite repository.

$ /opt/VRTS/bin/dbed_update -S $ORACLE_SID -H $ORACLE_HOME

2 By default, the repository is created on the file system which contains the Oracle

SYSTEM tablespace. If you need an alternative repository path, first verify the following requirements:

Repository path has to be a directory writable by Oracle user.

The update commands will not be able to verify accessibility of the repository path and will fail if you have not set up the path correctly.

Create an alternate repository path.

$ /opt/VRTS/bin/dbed_update -S $ORACLE_SID -H $ORACLE_HOME -R \

Alternate_path

3 If you are using Database Flashsnap for off-host processing, and if you have a repository on the secondary host that you need to migrate: perform the previous steps on the secondary host.

Performing post-upgrade tasks

Post upgrade tasks for migrating the SFDB repository database

146

4 On the primary host, edit your snapplans to remove the

"SNAPSHOT_DG=SNAP_*" parameter and add

“SNAPSHOT_DG_PREFIX=SNAP_*". The parameter can be any PREFIX value and not necessarily "SNAP_*".

For example:

$ /usr/oracle> more SNAPPLAN1

SNAPSHOT_VERSION=5.0

PRIMARY_HOST=system1

SECONDARY_HOST=system1.example.com

PRIMARY_DG=system1_data

SNAPSHOT_DG=SNAP_system1_data

ORACLE_SID=HN1

ARCHIVELOG_DEST=/oracle/orahome/dbs/arch

SNAPSHOT_ARCHIVE_LOG=yes

SNAPSHOT_MODE=online

SNAPSHOT_PLAN_FOR=database

SNAPSHOT_PLEX_TAG=dbed_flashsnap

SNAPSHOT_VOL_PREFIX=SNAP_

ALLOW_REVERSE_RESYNC=no

SNAPSHOT_MIRROR=1

$ /usr/oracle> more SNAPPLAN1

SNAPSHOT_VERSION=5.0

PRIMARY_HOST=system1

SECONDARY_HOST=system1.example.com

PRIMARY_DG=judge_data

SNAPSHOT_DG_PREFIX=SNAP_system1_data

ORACLE_SID=HN1

ARCHIVELOG_DEST=/oracle/orahome/dbs/arch

SNAPSHOT_ARCHIVE_LOG=yes

SNAPSHOT_MODE=online

SNAPSHOT_PLAN_FOR=database

SNAPSHOT_PLEX_TAG=dbed_flashsnap

SNAPSHOT_VOL_PREFIX=SNAP_

ALLOW_REVERSE_RESYNC=no

SNAPSHOT_MIRROR=1

Performing post-upgrade tasks

Recovering VVR if automatic upgrade fails

147

5 On the primary host, revalidate your snapshots using the following command:

$ /opt/VRTS/bin/vxsfadm -s flashsnap \

-a oracle -c SNAPPLAN -o validate

This completes the migration of the repository for Database Storage

Checkpoints and Database Tiered Storage parameters.

Note: While you revalidate the snapshot configuration file ( snapplan

) from an older release, use the vxsfadm -c <configfile> option to avoid the default values from overriding the old values.

To begin using the Storage Foundation for Databases (SFDB) tools:

See Storage Foundation: Storage and Availability Management for Oracle Databases

Migrating SFDB from 5.0x to 6.2

When upgrading from SF version 5.0 to SF 6.2 the S*vxdbms3 startup script is renamed to NO_S*vxdbms3. The S*vxdbms3 startup script is required by sfua_rept_migrate . Thus when sfua_rept_migrate is run, it is unable to find the

S*vxdbms3 startup script and gives the error message:

/etc/rc.d/rc2.d/S*vxdbms3 not found

SFORA sfua_rept_migrate ERROR V-81-3558 File: is missing.

SFORA sfua_rept_migrate ERROR V-81-9160 Failed to mount repository.

To prevent S*vxdbms3 startup script error

◆ Rename the startup script NO_S*vxdbms3 to S*vxdbms3.

Recovering VVR if automatic upgrade fails

If the upgrade fails during the configuration phase, after displaying the VVR upgrade directory, the configuration needs to be restored before the next attempt. Run the scripts in the upgrade directory in the following order to restore the configuration:

# restoresrl

# adddcm

# srlprot

# attrlink

# start.rvg

After the configuration is restored, the current step can be retried.

Performing post-upgrade tasks

Upgrading disk layout versions

148

Upgrading disk layout versions

In this release, you can create and mount only file systems with disk layout Version

7, 8, 9, and 10. You can only local mount disk layout Version 6 only to upgrade to a later disk layout version.

Note: If you plan to use 64-bit quotas, you must upgrade to the latest disk layout

Version 10. The use of 64-bit quota on earlier disk layout versions is deprecated in this release.

Disk layout Version 6 has been deprecated and you cannot cluster mount an existing file system that has disk layout Version 6. To upgrade a cluster file system with disk layout Version 6, you must local mount the file system and then upgrade the file system using the vxupgrade utility to a later version.

To upgrade the disk layout versions

◆ To get to disk layout Version 10 from Version 6. You must incrementally upgrade the disk layout of this file system. For example:

# vxupgrade -n 7 /mnt

# vxupgrade -n 8 /mnt

# vxupgrade -n 9 /mnt

# vxupgrade -n 10 /mnt

See the vxupgrade

(1M) manual page.

Support for disk layout Version 4 has been removed. You must upgrade any existing file systems with disk layout Version 4 to disk layout Version 7 or later using the vxfsconvert command.

See the vxfsconvert

(1M) manual page.

Note: Symantec recommends that you upgrade existing file systems to the highest supported disk layout version prior to upgrading to this release. Once a disk layout version has been upgraded, it is not possible to downgrade to the previous version.

You can check which disk layout version your file system has by using the following command:

# fstyp -v /dev/vx/dsk/dg1/vol1 | grep -i version

For more information about disk layout versions, see the Symantec Storage

Foundation Administrator's Guide.

Performing post-upgrade tasks

Upgrading VxVM disk group versions

149

Upgrading VxVM disk group versions

All Veritas Volume Manager disk groups have an associated version number. Each

VxVM release supports a specific set of disk group versions. VxVM can import and perform tasks on disk groups with those versions. Some new features and tasks work only on disk groups with the current disk group version. Before you can perform the tasks or use the features, upgrade the existing disk groups.

For 6.2, the Veritas Volume Manager disk group version is different than in previous

VxVM releases. Symantec recommends that you upgrade the disk group version if you upgraded from a previous VxVM release.

After upgrading to SF 6.2, you must upgrade any existing disk groups that are organized by ISP. Without the version upgrade, configuration query operations continue to work fine. However, configuration change operations will not function correctly.

For more information about ISP disk groups, refer to the Symantec Storage

Foundation Administrator's Guide.

Use the following command to find the version of a disk group:

# vxdg list diskgroup

To upgrade a disk group to the current disk group version, use the following command:

# vxdg upgrade diskgroup

For more information about disk group versions, see the Symantec Storage

Foundation Administrator's Guide.

Updating variables

In

/etc/profile

, update the

PATH and

MANPATH variables as needed.

MANPATH can include /opt/VRTS/man and PATH can include /opt/VRTS/bin .

Setting the default disk group

You may find it convenient to create a system-wide default disk group. The main benefit of creating a default disk group is that VxVM commands default to the default disk group. You do not need to use the

-g option.

You can set the name of the default disk group after installation by running the following command on a system:

Performing post-upgrade tasks

Verifying the Storage Foundation upgrade

150

# vxdctl defaultdg diskgroup

See the Symantec Storage Foundation Administrator’s Guide.

Verifying the Storage Foundation upgrade

Refer to the section about verifying the installation to verify the upgrade.

See

“Verifying that the products were installed”

on page 155.

Section

5

Post-installation tasks

Chapter 17. Performing post-installation tasks

Chapter 18. Verifying the SF installation

Chapter

17

Performing post-installation tasks

This chapter includes the following topics:

Switching on Quotas

Enabling DMP support for native devices

About configuring authentication for SFDB tools

Switching on Quotas

This turns on the group and user quotas once all the nodes are upgraded to 6.2, if it was turned off earlier.

To turn on the group and user quotas

◆ Switch on quotas:

# vxquotaon -av

Enabling DMP support for native devices

Symantec Dynamic Multi-Pathing (DMP) is a component of SF. DMP supports

Veritas Volume Manager (VxVM) volumes on DMP metadevices, and Veritas File

System (VxFS) file systems on those volumes.

DMP can also provide multi-pathing functionality for the native operating system volumes and file systems on DMP devices.

For more information on using DMP with native devices, see the Symantec Dynamic

Multi-Pathing Administrator's Guide.

Performing post-installation tasks

About configuring authentication for SFDB tools

153

After you install SF for the first time, use the following procedure to enable DMP support for native devices.

If DMP native support for native devices is enabled on a system before you upgrade

SF, DMP native support is maintained when SF is upgraded.

To enable DMP support for native devices

◆ Turn on the tunable parameter to enable DMP support:

# vxdmpadm set dmp_native_support=on

The dmp_native_support parameter is persistent.

About configuring authentication for SFDB tools

To configure authentication for Storage Foundation for Databases (SFDB) tools, perform the following tasks:

Configure the vxdbd daemon to require authentication

Add a node to a cluster that is using authentication for SFDB tools

See

“Configuring vxdbd for SFDB tools authentication”

on page 153.

Configuring vxdbd for SFDB tools authentication

To configure vxdbd, perform the following steps as the root user

1 Run the sfae_auth_op command to set up the authentication services.

# /opt/VRTS/bin/sfae_auth_op -o setup

Setting up AT

Starting SFAE AT broker

Creating SFAE private domain

Backing up AT configuration

Creating principal for vxdbd

2 Stop the vxdbd daemon.

# /opt/VRTS/bin/sfae_config disable vxdbd has been disabled and the daemon has been stopped.

Performing post-installation tasks

About configuring authentication for SFDB tools

154

3 Enable authentication by setting the

AUTHENTICATION key to yes in the

/etc/vx/vxdbed/admin.properties

configuration file.

If /etc/vx/vxdbed/admin.properties

does not exist, then use cp

/opt/VRTSdbed/bin/admin.properties.example

/etc/vx/vxdbed/admin.properties

.

4 Start the vxdbd daemon.

# /opt/VRTS/bin/sfae_config enable vxdbd has been enabled and the daemon has been started.

It will start automatically on reboot.

The vxdbd daemon is now configured to require authentication.

Chapter

18

Verifying the SF installation

This chapter includes the following topics:

Verifying that the products were installed

Installation log files

Starting and stopping processes for the Symantec products

Checking Veritas Volume Manager processes

Verifying that the products were installed

Verify that the SF products are installed.

Use the command to check which RPMs have been installed.

# rpm -qa | grep VRTS

You can verify the version of the installed product. Use the following command:

# /opt/VRTS/install/installsf<version> -version

Where <version> is the specific release version.

You can find out the about the installed RPMs and its versions by using the following command:

# /opt/VRTS/install/showversion

See

“About the script-based installer”

on page 41.

Use the following sections to further verify the product installation.

Verifying the SF installation

Installation log files

156

Installation log files

After every product installation, the installer creates three text files:

■ Installation log file

Response file

■ Summary file

The name and location of each file is displayed at the end of a product installation, and are always located in the /opt/VRTS/install/logs directory. It is recommended that you keep the files for auditing, debugging, and future use.

Using the installation log file

The installation log file contains all commands executed during the procedure, their output, and errors generated by the commands. This file is for debugging installation problems and can be used for analysis by Symantec Support.

Using the summary file

The summary file contains the results of the installation by the installer or product installation scripts. The summary includes the list of the RPMs, and the status

(success or failure) of each RPM. The summary also indicates which processes were stopped or restarted during the installation. After installation, refer to the summary file to determine whether any processes need to be started.

Starting and stopping processes for the Symantec products

After the installation and configuration is complete, the Symantec product installer starts the processes that the installed products use. You can use the product installer to stop or start the processes, if required.

Verifying the SF installation

Checking Veritas Volume Manager processes

157

To stop the processes

◆ Use the -stop option to stop the product installation script.

For example, to stop the product's processes, enter the following command:

# ./installer -stop or

# /opt/VRTS/install/installsf<version> -stop

Where

<version> is the specific release version.

See

“About the script-based installer”

on page 41.

To start the processes

Use the -start option to start the product installation script.

For example, to start the product's processes, enter the following command:

# ./installer -start or

# /opt/VRTS/install/installsf<version> -start

Where <version> is the specific release version.

See

“About the script-based installer”

on page 41.

Checking Veritas Volume Manager processes

Use the following procedure to verify that Volume Manager processes are running.

To confirm that key Volume Manager processes are running

◆ Type the following command:

# ps -ef | grep vx

Entries for the vxiod

, vxconfigd

, vxnotify

, vxesd

, vxrelocd

, vxcached and vxconfigbackupd processes should appear in the output from this command.

If you disable hot-relocation, the vxrelocd and vxnotify processes are not displayed.

Section

6

Uninstallation of SF

Chapter 19. Uninstalling Storage Foundation

Chapter 20. Uninstalling SF using response files

Chapter

19

Uninstalling Storage

Foundation

This chapter includes the following topics:

Removing VxFS file systems

Removing rootability

Moving volumes to disk partitions

Removing the Replicated Data Set

Uninstalling SF RPMs using the script-based installer

Uninstalling SF with the web-based installer

Removing license files (Optional)

Removing the Storage Foundation for Databases (SFDB) repository

Removing VxFS file systems

The VxFS RPM cannot be removed if there are any mounted VxFS file systems.

Unmount all VxFS file systems before removing the RPM. After you remove the

VxFS RPM, VxFS file systems are not mountable or accessible until another VxFS

RPM is installed. It is advisable to back up VxFS file systems before installing a new VxFS RPM. If VxFS will not be installed again, all VxFS file systems must be converted to a new file system type.

Uninstalling Storage Foundation

Removing rootability

160

To remove VxFS file systems

1 Check if any VxFS file systems or Storage Checkpoints are mounted:

# df -T | grep vxfs

2 Make backups of all data on the file systems that you wish to preserve, or recreate them as non-VxFS file systems on non-VxVM volumes or partitions.

3 Unmount all Storage Checkpoints and file systems:

# umount /checkpoint_name

# umount /filesystem

4 Comment out or remove any VxFS file system entries from the /etc/fstab file.

Removing rootability

Perform this procedure if you configured rootability by encapsulating the root disk.

Uninstalling Storage Foundation

Moving volumes to disk partitions

161

To remove rootability

1 Check if the system’s root disk is under VxVM control by running this command:

# df -v /

The root disk is under VxVM control if

/dev/vx/dsk/rootdg/rootvol is listed as being mounted as the root (

/

) file system. If so, unmirror and unencapsulate the root disk as described in the following steps:

2 Use the vxplex command to remove all the plexes of the volumes rootvol , swapvol

, usr

, var

, opt and home that are on disks other than the root disk.

For example, the following command removes the plexes mirrootvol-01 , and mirswapvol-01 that are configured on a disk other than the root disk:

# vxplex -o rm dis mirrootvol-01 mirswapvol-01

Warning: Do not remove the plexes that correspond to the original root disk partitions.

3 Enter the following command to convert all the encapsulated volumes in the root disk back to being accessible directly through disk partitions instead of through volume devices:

# /etc/vx/bin/vxunroot

Following the removal of encapsulation, the system is rebooted from the unencapsulated root disk.

Moving volumes to disk partitions

All volumes must be moved to disk partitions.

This can be done using one of the following procedures:

■ Back up the system fully onto tape and then recover from it.

Back up each file system individually and then recover them all after creating new file systems on disk partitions.

Use VxVM to move volumes incrementally onto disk partitions as described in the following section.

Moving volumes onto disk partitions using VxVM

Use the following procedure to move volumes onto disk partitions.

Uninstalling Storage Foundation

Moving volumes to disk partitions

162

To move volumes onto disk partitions

1 Evacuate disks using the vxdiskadm program or the vxevac script. You should consider the amount of target disk space required for this before you begin.

Evacuation moves subdisks from the specified disks to target disks. The evacuated disks provide the initial free disk space for volumes to be moved to disk partitions.

2 Remove the evacuated disks from VxVM control using the following commands:

# vxdg -g diskgroup rmdisk disk _media_name

# vxdisk rm disk_access_name

3 Decide which volume to move first. If the volume to be moved is mounted, unmount it.

4 If the volume is being used as a raw partition for database applications, make sure that the application is not updating the volume and that data on the volume is synced.

5 Create a partition on free disk space of the same size as the volume. If there is not enough free space for the partition, a new disk must be added to the system for the first volume removed. Subsequent volumes can use the free space generated by the removal of this volume.

6

Copy the data on the volume onto the newly created disk partition using a command similar to the following:

# dd if=/dev/vx/dsk/diskgroup/volume-name of=/dev/sdb2 where sdb is the disk outside of VxVM and

2 is the newly created partition on that disk.

7 Replace the entry for that volume (if present) in

/etc/fstab with an entry for the newly created partition.

8 Mount the disk partition if the corresponding volume was previously mounted.

9 Stop the volume and remove it from VxVM using the following commands:

# vxvol -g diskgroup -f stop volume_name

# vxedit -g diskgroup -rf rm volume_name

10 Remove any disks that have become free (have no subdisks defined on them) by removing volumes from VxVM control. To check if there are still some subdisks remaining on a particular disk, use the following command:

# vxprint -F "%sdnum" disk_media_name

Uninstalling Storage Foundation

Removing the Replicated Data Set

163

11 If the output is not 0, there are still some subdisks on this disk that must be subsequently removed. If the output is 0, remove the disk from VxVM control using the following commands:

# vxdg -g diskgroup rmdisk disk_media_name

# vxdisk rm disk_access_name

12 The free space now created can be used for adding the data in the next volume to be removed.

13 After all volumes have been converted into disk partitions successfully, reboot the system. After the reboot, none of the volumes should be open. To verify that none of the volumes are open, use the following command:

# vxprint -Aht -e v_open

14 If any volumes remain open, repeat the steps listed above.

Removing the Replicated Data Set

If you use VVR, you need to perform the following steps. This section gives the steps to remove a Replicated Data Set (RDS) when the application is either active or stopped.

Note: If you are upgrading Volume Replicator, do not remove the Replicated Data

Set.

Uninstalling Storage Foundation

Removing the Replicated Data Set

164

To remove the Replicated Data Set

1 Verify that all RLINKs are up-to-date:

# vxrlink -g diskgroup status rlink_name

If the Secondary is not required to be up-to-date, proceed to

2

and stop replication using the

-f option with the vradmin stoprep command.

2 Stop replication to the Secondary by issuing the following command on any host in the RDS:

The vradmin stoprep command fails if the Primary and Secondary RLINKs are not up-to-date. Use the

-f option to stop replication to a Secondary even when the RLINKs are not up-to-date.

# vradmin -g diskgroup stoprep local_rvgname sec_hostname

The argument local_rvgname is the name of the RVG on the local host and represents its RDS.

The argument sec_hostname is the name of the Secondary host as displayed in the output of the vradmin printrvg command.

3 Remove the Secondary from the RDS by issuing the following command on any host in the RDS:

# vradmin -g diskgroup delsec local_rvgname sec_hostname

The argument local_rvgname is the name of the RVG on the local host and represents its RDS.

The argument sec_hostname is the name of the Secondary host as displayed in the output of the vradmin printrvg command.

4 Remove the Primary from the RDS by issuing the following command on the

Primary:

# vradmin -g diskgroup delpri local_rvgname

When used with the

-f option, the vradmin delpri command removes the

Primary even when the application is running on the Primary.

The RDS is removed.

5 If you want to delete the SRLs from the Primary and Secondary hosts in the

RDS, issue the following command on the Primary and all Secondaries:

# vxedit -r -g diskgroup rm srl_name

Uninstalling Storage Foundation

Uninstalling SF RPMs using the script-based installer

165

Uninstalling SF RPMs using the script-based installer

Use the following procedure to remove SF products.

Not all RPMs may be installed on your system depending on the choices that you made when you installed the software.

Note: After you uninstall the product, you cannot access any file systems you created using the default disk layout version in SF 6.2 with a previous version of SF.

To shut down and remove the installed SF RPMs

1 Comment out or remove any Veritas File System (VxFS) entries from the file system table /etc/fstab . Failing to remove these entries could result in system boot problems later.

2 Unmount all mount points for VxFS file systems.

# umount /mount_point

3 If the VxVM RPM (

VRTSvxvm

) is installed, read and follow the uninstallation procedures for VxVM.

See

“Removing rootability”

on page 160.

4 If a cache area is online, you must take the cache area offline before uninstalling the VxVM RPM. Use the following command to take the cache area offline:

# sfcache offline cachename

5 Make sure you have performed all of the prerequisite steps.

6 Move to the

/opt/VRTS/install directory and run the uninstall script.

# cd /opt/VRTS/install

# ./uninstallsf<version>

Where

<version> is the specific release version.

Or, if you are using rsh, use the following:

# ./uninstallsf<version> -rsh

See

“About the script-based installer”

on page 41.

Uninstalling Storage Foundation

Uninstalling SF with the web-based installer

166

7 The uninstall script prompts for the system name. Enter one or more system names, separated by a space, from which to uninstall SF, for example, sys1

:

Enter the system names separated by spaces: [q?] sys1 sys2

8 The uninstall script prompts you to stop the product processes. If you respond yes, the processes are stopped and the RPMs are uninstalled.

The uninstall script creates log files and displays the location of the log files.

9 Most RPMs have kernel components. In order to ensure complete removal, a system reboot is recommended after all RPMs have been removed.

10 In case the uninstallation fails to remove any of the VRTS RPMs, check the installer logs for the reason for failure or try to remove the RPMs manually using the pkgrm command. For example: pkgrm VRTSvxvm

Uninstalling SF with the web-based installer

This section describes how to uninstall using the web-based installer.

Note: After you uninstall the product, you cannot access any file systems you created using the default disk layout version in SF 6.2 with a previous version of SF.

To uninstall SF

1 Perform the required steps to save any data that you want to preserve. For example, take backups of configuration files.

2 Start the web-based installer.

See

“Starting the web-based installer”

on page 48.

3 On the Select a task and a product page, select Uninstall a Product from the

Task drop-down list.

4 Select Storage Foundation from the Product drop-down list, and click Next.

5 Indicate the systems on which to uninstall. Enter one or more system names, separated by spaces. Click Next.

6 After the validation completes successfully, click Next to uninstall SF on the selected system.

7 If there are any processes running on the target system, the installer stops the processes. Click Next.

Uninstalling Storage Foundation

Removing license files (Optional)

167

8 After the installer stops the processes, the installer removes the products from the specified system.

Click Next.

9 After the uninstall completes, the installer displays the location of the summary, response, and log files. If required, view the files to confirm the status of the removal.

10 Click Finish.

Most RPMs have kernel components. To ensure their complete removal, a system restart is recommended after all the RPMs have been removed.

Removing license files (Optional)

Optionally, you can remove the license files.

To remove the Veritas license files

1 To see what license key files you have installed on a system, enter:

# /sbin/vxlicrep

The output lists the license keys and information about their respective products.

2 Go to the directory containing the license key files and list them:

# cd /etc/vx/licenses/lic

# ls -a

3 Using the output from step 1, identify and delete the unwanted key files that are listed in step 2. Unwanted keys may be deleted by removing the license key file.

Removing the Storage Foundation for Databases

(SFDB) repository

After removing the product, you can remove the SFDB repository file and any backups.

Removing the SFDB repository file disables the SFDB tools.

Uninstalling Storage Foundation

Removing the Storage Foundation for Databases (SFDB) repository

168

To remove the SFDB repository

1 Identify the SFDB repositories created on the host.

Oracle:

# cat /var/vx/vxdba/rep_loc

{

"sfae_rept_version" : 1,

"oracle" : {

"SFAEDB" : {

"location" : "/data/sfaedb/.sfae",

"old_location" : "",

"alias" : [

"sfaedb"

]

}

}

}

2 Remove the directory identified by the location key.

Oracle:

# rm -rf /data/sfaedb/.sfae

DB2 9.5 and 9.7:

# rm -rf /db2data/db2inst1/NODE0000/SQL00001/.sfae

DB2 10.1 and 10.5:

# rm -rf /db2data/db2inst1/NODE0000/SQL00001/MEMBER0000/.sfae

3 Remove the repository location file.

# rm -rf /var/vx/vxdba/rep_loc

This completes the removal of the SFDB repository.

Chapter

20

Uninstalling SF using response files

This chapter includes the following topics:

Uninstalling SF using response files

Response file variables to uninstall Storage Foundation

Sample response file for SF uninstallation

Uninstalling SF using response files

Typically, you can use the response file that the installer generates after you perform

SF uninstallation on one system to uninstall SF on other systems.

To perform an automated uninstallation

1 Make sure that you meet the prerequisites to uninstall SF.

2 Copy the response file to the system where you want to uninstall SF.

3 Edit the values of the response file variables as necessary.

4 Start the uninstallation from the system to which you copied the response file.

For example:

# /opt/VRTS/install/uninstallsf<version>

-responsefile /tmp/response_file

Where

<version> is the specific release version, and /tmp/response_file is the response file’s full path name.

See

“About the script-based installer”

on page 41.

Uninstalling SF using response files

Response file variables to uninstall Storage Foundation

170

Response file variables to uninstall Storage

Foundation

Table 20-1

lists the response file variables that you can define to configure SF.

Response file variables for uninstalling SF Table 20-1

Variable

CFG{systems}

CFG{prod}

CFG{opt}{keyfile}

CFG{opt}{tmppath}

CFG{opt}{logpath}

CFG{opt}{uninstall}

Description

List of systems on which the product is to be installed or uninstalled.

List or scalar: list

Optional or required: required

Defines the product to be installed or uninstalled.

List or scalar: scalar

Optional or required: required

Defines the location of an ssh keyfile that is used to communicate with all remote systems.

List or scalar: scalar

Optional or required: optional

Defines the location where a working directory is created to store temporary files and the RPMs that are needed during the install. The default location is /var/tmp.

List or scalar: scalar

Optional or required: optional

Mentions the location where the log files are to be copied.

The default location is /opt/VRTS/install/logs.

List or scalar: scalar

Optional or required: optional

Uninstalls SF RPMs.

List or scalar: scalar

Optional or required: optional

Sample response file for SF uninstallation

The following example shows a response file for uninstalling Storage Foundation.

Uninstalling SF using response files

Sample response file for SF uninstallation

171 our %CFG;

$CFG{opt}{redirect}=1;

$CFG{opt}{uninstall}=1;

$CFG{prod}="SF62";

$CFG{systems}=[ qw(thoropt89 thoropt90) ];

1;

Section

7

Installation reference

Appendix A. Installation scripts

Appendix B. Tunable files for installation

Appendix C. Configuring the secure shell or the remote shell for communications

Appendix D. Storage Foundation components

Appendix E. Troubleshooting installation issues

Appendix F. Compatability issues when installing Storage Foundation with other products

Appendix

A

Installation scripts

This appendix includes the following topics:

Installation script options

Installation script options

Table A-1

shows command line options for the installation script. For an initial install or upgrade, options are not usually required. The installation script options apply to all Symantec Storage Foundation product scripts, except where otherwise noted.

See

“About the script-based installer”

on page 41.

Table A-1 Available command line options

Command Line Option

-allpkgs

-comcleanup

-comsetup

-configure

Function

Displays all RPMs required for the specified product. The RPMs are listed in correct installation order. The output can be used to create scripts for command line installs, or for installations over a network.

The -comcleanup option removes the secure shell or remote shell configuration added by installer on the systems. The option is only required when installation routines that performed auto-configuration of the shell are abruptly terminated.

The -comsetup option is used to set up the ssh or rsh communication between systems without requests for passwords or passphrases.

Configures the product after installation.

Installation scripts

Installation script options

174

Table A-1 Available command line options (continued)

Command Line Option

–hostfile full_path_to_file

-disable_dmp_native_support

Function

Specifies the location of a file that contains a list of hostnames on which to install.

Disables Dynamic Multi-pathing support for the native LVM volume groups and ZFS pools during upgrade. Retaining Dynamic Multi-pathing support for the native LVM volume groups and ZFS pools during upgrade increases RPM upgrade time depending on the number of LUNs and native LVM volume groups and ZFS pools configured on the system.

-online_upgrade

-patch_path

-patch2_path

-patch3_path

-patch4_path

-patch5_path

-installallpkgs

Used to perform online upgrade. Using this option, the installer upgrades the whole cluster and also supports customer's application zero down time during the upgrade procedure. Now this option only supports VCS and ApplicationHA.

Defines the path of a patch level release to be integrated with a base or a maintenance level release in order for multiple releases to be simultaneously installed .

Defines the path of a second patch level release to be integrated with a base or a maintenance level release in order for multiple releases to be simultaneously installed.

Defines the path of a third patch level release to be integrated with a base or a maintenance level release in order for multiple releases to be simultaneously installed.

Defines the path of a fourth patch level release to be integrated with a base or a maintenance level release in order for multiple releases to be simultaneously installed.

Defines the path of a fifth patch level release to be integrated with a base or a maintenance level release in order for multiple releases to be simultaneously installed.

The -installallpkgs option is used to select all RPMs.

Installation scripts

Installation script options

175

Table A-1 Available command line options (continued)

Command Line Option

-installrecpkgs

Function

The -installrecpkgsoption is used to select the recommended RPMs set.

–installminpkgs

-ignorepatchreqs

–keyfile ssh_key_file

–kickstart dir_path

-license

–logpath log_path

-makeresponsefile

-minpkgs

-noipc

The -installminpkgsoption is used to select the minimum RPMs set.

The -ignorepatchreqs option is used to allow installation or upgrading even if the prerequisite

RPMs or patches are missed on the system.

Specifies a key file for secure shell (SSH) installs.

This option passes -I ssh_key_file to every

SSH invocation.

Produces a kickstart configuration file for installing with Linux RHEL Kickstart. The file contains the list of Symantec RPMs in the correct order for installing, in a format that can be used for Kickstart installations. The dir_path indicates the path to the directory in which to create the file.

Registers or updates product licenses on the specified systems.

Specifies a directory other than

/opt/VRTS/install/logs as the location where installer log files, summary files, and response files are saved.

Use the -makeresponsefile option only to generate response files. No actual software installation occurs when you use this option.

Displays the minimal RPMs required for the specified product. The RPMs are listed in correct installation order. Optional RPMs are not listed.

The output can be used to create scripts for command line installs, or for installations over a network. See allpkgs option.

Disables the installer from making outbound networking calls to Symantec Operations

Readiness Tool (SORT) in order to automatically obtain patch and release information updates.

Installation scripts

Installation script options

176

Table A-1

–pkginfo

Available command line options (continued)

Command Line Option

-nolic

Function

Allows installation of product RPMs without entering a license key. Licensed features cannot be configured, started, or used when this option is specified.

Displays a list of RPMs and the order of installation in a human-readable format. This option only applies to the individual product installation scripts.

For example, use the -pkginfo option with the installvcs script to display VCS RPMs.

–pkgset

-pkgtable

–postcheck

-precheck

-prod

–recpkgs

-redirect

-require

-requirements

Discovers and displays the RPM group (minimum, recommended, all) and RPMs that are installed on the specified systems.

Displays product's RPMs in correct installation order by group.

Checks for different HA and file system-related processes, the availability of different ports, and the availability of cluster-related service groups.

Performs a preinstallation check to determine if systems meet all installation requirements.

Symantec recommends doing a precheck before installing a product.

Specifies the product for operations.

Displays the recommended RPMs required for the specified product. The RPMs are listed in correct installation order. Optional RPMs are not listed.

The output can be used to create scripts for command line installs, or for installations over a network. See allpkgs option.

Displays progress details without showing the progress bar.

Specifies an installer patch file.

The -requirements option displays required OS version, required RPMs and patches, file system space, and other system requirements in order to install the product.

Installation scripts

Installation script options

177

Table A-1 Available command line options (continued)

Command Line Option

–responsefile response_file

Function

Automates installation and configuration by using system and configuration information stored in a specified file instead of prompting for information.

The response_file must be a full path name. You must edit the response file to use it for subsequent installations. Variable field definitions are defined within the file.

-rsh

–serial

-settunables

-start

-stop

-timeout

Specify this option when you want to use RSH and

RCP for communication between systems instead of the default SSH and SCP.

See

“About configuring secure shell or remote shell communication modes before installing products”

on page 192.

Specifies that the installation script performs install, uninstall, start, and stop operations on each system in a serial fashion. If this option is not specified, these operations are performed simultaneously on all systems.

Specify this option when you want to set tunable parameters after you install and configure a product. You may need to restart processes of the product for the tunable parameter values to take effect. You must use this option together with the

-tunablesfile option.

Starts the daemons and processes for the specified product.

Stops the daemons and processes for the specified product.

The -timeout option is used to specify the number of seconds that the script should wait for each command to complete before timing out.

Setting the -timeout option overrides the default value of 1200 seconds. Setting the -timeout option to 0 prevents the script from timing out. The

-timeout option does not work with the -serial option

Installation scripts

Installation script options

178

Table A-1 Available command line options (continued)

Command Line Option

–tmppath tmp_path

Function

Specifies a directory other than /var/tmp as the working directory for the installation scripts. This destination is where initial logging is performed and where RPMs are copied on remote systems before installation.

-tunables

-tunables_file tunables_file

-upgrade

-version

-yumgroupxml

Lists all supported tunables and create a tunables file template.

Specify this option when you specify a tunables file. The tunables file should include tunable parameters.

Specifies that an existing version of the product exists and you plan to upgrade it.

Checks and reports the installed products and their versions. Identifies the installed and missing RPMs and patches where applicable for the product.

Provides a summary that includes the count of the installed and any missing RPMs and patches where applicable. Lists the installed patches, patches, and available updates for the installed product if an Internet connection is available.

The -yumgroupxml option is used to generate a yum group definition XML file. The createrepo command can use the file on Redhat Linux to create a yum group for automated installation of all RPMs for a product. An available location to store the XML file should be specified as a complete path. The -yumgroupxml option is supported on Redhat Linux only.

Appendix

B

Tunable files for installation

This appendix includes the following topics:

About setting tunable parameters using the installer or a response file

Setting tunables for an installation, configuration, or upgrade

Setting tunables with no other installer-related operations

Setting tunables with an un-integrated response file

Preparing the tunables file

Setting parameters for the tunables file

Tunables value parameter definitions

About setting tunable parameters using the installer or a response file

You can set non-default product and system tunable parameters using a tunables file. With the file, you can set tunables such as the I/O policy or toggle native multi-pathing. The tunables file passes arguments to the installer script to set tunables. With the file, you can set the tunables for the following operations:

■ When you install, configure, or upgrade systems.

# ./installer -tunablesfile tunables_file_name

See

“Setting tunables for an installation, configuration, or upgrade”

on page 180.

When you apply the tunables file with no other installer-related operations.

# ./installer -tunablesfile tunables_file_name -settunables [

sys1 sys2 ...]

Tunable files for installation

Setting tunables for an installation, configuration, or upgrade

180

See

“Setting tunables with no other installer-related operations”

on page 181.

When you apply the tunables file with an un-integrated response file.

# ./installer -responsefile response_file_name -tunablesfile tunables_file_name

See

“Setting tunables with an un-integrated response file”

on page 182.

See

“About response files”

on page 27.

You must select the tunables that you want to use from this guide.

See

“Tunables value parameter definitions”

on page 184.

Setting tunables for an installation, configuration, or upgrade

You can use a tunables file for installation procedures to set non-default tunables.

You invoke the installation script with the tunablesfile option. The tunables file passes arguments to the script to set the selected tunables. You must select the tunables that you want to use from this guide.

See

“Tunables value parameter definitions”

on page 184.

Note: Certain tunables only take effect after a system reboot.

To set the non-default tunables for an installation, configuration, or upgrade

1 Prepare the tunables file.

See

“Preparing the tunables file”

on page 183.

2 Make sure the systems where you want to install SF meet the installation requirements.

3 Complete any preinstallation tasks.

4 Copy the tunables file to one of the systems where you want to install, configure, or upgrade the product.

5 Mount the product disc and navigate to the directory that contains the installation program.

Tunable files for installation

Setting tunables with no other installer-related operations

181

6 Start the installer for the installation, configuration, or upgrade. For example:

# ./installer -tunablesfile /tmp/tunables_file

-settunables [sys1 sys2 ...]

Where /tmp/tunables_file is the full path name for the tunables file.

7 Proceed with the operation. When prompted, accept the tunable parameters.

Certain tunables are only activated after a reboot. Review the output carefully to determine if the system requires a reboot to set the tunable value.

8 The installer validates the tunables. If an error occurs, exit the installer and check the tunables file.

Setting tunables with no other installer-related operations

You can use the installer to set tunable parameters without any other installer-related operations. You must use the parameters described in this guide. Note that many of the parameters are product-specific. You must select the tunables that you want to use from this guide.

See

“Tunables value parameter definitions”

on page 184.

Note: Certain tunables only take effect after a system reboot.

To set tunables with no other installer-related operations

1 Prepare the tunables file.

See

“Preparing the tunables file”

on page 183.

2 Make sure the systems where you want to install SF meet the installation requirements.

3 Complete any preinstallation tasks.

4 Copy the tunables file to one of the systems that you want to tune.

5 Mount the product disc and navigate to the directory that contains the installation program.

6 Start the installer with the

-settunables option.

# ./installer -tunablesfile tunables_file_name -settunables [

sys123 sys234 ...]

Where /tmp/tunables_file is the full path name for the tunables file.

Tunable files for installation

Setting tunables with an un-integrated response file

182

7 Proceed with the operation. When prompted, accept the tunable parameters.

Certain tunables are only activated after a reboot. Review the output carefully to determine if the system requires a reboot to set the tunable value.

8 The installer validates the tunables. If an error occurs, exit the installer and check the tunables file.

Setting tunables with an un-integrated response file

You can use the installer to set tunable parameters with an un-integrated response file. You must use the parameters described in this guide. Note that many of the parameters are product-specific. You must select the tunables that you want to use from this guide.

See

“Tunables value parameter definitions”

on page 184.

Note: Certain tunables only take effect after a system reboot.

To set tunables with an un-integrated response file

1 Make sure the systems where you want to install SF meet the installation requirements.

2 Complete any preinstallation tasks.

3 Prepare the tunables file.

See

“Preparing the tunables file”

on page 183.

4 Copy the tunables file to one of the systems that you want to tune.

5 Mount the product disc and navigate to the directory that contains the installation program.

6 Start the installer with the -responsefile and -tunablesfile options.

# ./installer -responsefile response_file_name -tunablesfile tunables_file_name

Where response_file_name is the full path name for the response file and

tunables_file_name is the full path name for the tunables file.

7 Certain tunables are only activated after a reboot. Review the output carefully to determine if the system requires a reboot to set the tunable value.

8 The installer validates the tunables. If an error occurs, exit the installer and check the tunables file.

Tunable files for installation

Preparing the tunables file

183

Preparing the tunables file

A tunables file is a Perl module and consists of an opening and closing statement, with the tunables defined between. Use the hash symbol at the beginning of the line to comment out the line. The tunables file opens with the line "our %TUN;" and ends with the return true "1;" line. The final return true line only needs to appear once at the end of the file. Define each tunable parameter on its own line.

You can use the installer to create a tunables file template, or manually format tunables files you create.

To create a tunables file template

◆ Start the installer with the

-tunables option. Enter the following:

# ./installer -tunables

You see a list of all supported tunables, and the location of the tunables file template.

To manually format tunables files

◆ Format the tunable parameter as follows:

$TUN{"tunable_name"}{"system_name"|"*"}=value_of_tunable;

For the system_name, use the name of the system, its IP address, or a wildcard symbol. The value_of_tunable depends on the type of tunable you are setting. End the line with a semicolon.

The following is an example of a tunables file.

#

# Tunable Parameter Values:

# our %TUN;

$TUN{"tunable1"}{"*"}=1024;

$TUN{"tunable3"}{"sys123"}="SHA256";

1;

Setting parameters for the tunables file

Each tunables file defines different tunable parameters. The values that you can use are listed in the description of each parameter. Select the tunables that you want to add to the tunables file and then configure each parameter.

Tunable files for installation

Tunables value parameter definitions

184

See

“Tunables value parameter definitions”

on page 184.

Each line for the parameter value starts with $TUN. The name of the tunable is in curly brackets and double-quotes. The system name is enclosed in curly brackets and double-quotes. Finally define the value and end the line with a semicolon, for example:

$TUN{"dmp_daemon_count"}{"node123"}=16;

In this example, you are changing the dmp_daemon_count value from its default of 10 to 16. You can use the wildcard symbol "*" for all systems. For example:

$TUN{"dmp_daemon_count"}{"*"}=16;

Tunables value parameter definitions

When you create a tunables file for the installer you can only use the parameters in the following list.

Prior to making any updates to the tunables, refer to the Symantec Storage

Foundation Cluster File System High Availability Administrator's Guide for detailed information on product tunable ranges and recommendations.

Table B-1

describes the supported tunable parameters that can be specified in a tunables file.

Table B-1 Supported tunable parameters

Tunable autoreminor autostartvolumes dmp_cache_open dmp_daemon_count dmp_delayq_interval

Description

(Veritas Volume Manager) Enable reminoring in case of conflicts during disk group import.

(Veritas Volume Manager) Enable the automatic recovery of volumes.

(Symantec Dynamic Multi-Pathing) Whether the first open on a device performed by an array support library (ASL) is cached.

(Symantec Dynamic Multi-Pathing) The number of kernel threads for DMP administrative tasks.

(Symantec Dynamic Multi-Pathing) The time interval for which DMP delays the error processing if the device is busy.

Tunable files for installation

Tunables value parameter definitions

185

Table B-1

Tunable dmp_fast_recovery

Supported tunable parameters (continued)

Description

(Symantec Dynamic Multi-Pathing) Whether

DMP should attempt to obtain SCSI error information directly from the HBA interface.

This tunable must be set after Symantec

Dynamic Multi-Pathing is started.

dmp_health_time dmp_log_level dmp_low_impact_probe dmp_lun_retry_timeout dmp_monitor_fabric dmp_monitor_osevent dmp_monitor_ownership dmp_native_support dmp_path_age dmp_pathswitch_blks_shift

(Symantec Dynamic Multi-Pathing) The time in seconds for which a path must stay healthy.

(Symantec Dynamic Multi-Pathing) The level of detail to which DMP console messages are displayed.

(Symantec Dynamic Multi-Pathing) Whether the low impact path probing feature is enabled.

(Symantec Dynamic Multi-Pathing) The retry period for handling transient errors.

(Symantec Dynamic Multi-Pathing) Whether the Event Source daemon (vxesd) uses the

Storage Networking Industry Association

(SNIA) HBA API. This tunable must be set after Symantec Dynamic Multi-Pathing is started.

(Symantec Dynamic Multi-Pathing) Whether the Event Source daemon (vxesd) monitors operating system events.

(Symantec Dynamic Multi-Pathing) Whether the dynamic change in LUN ownership is monitored.

(Symantec Dynamic Multi-Pathing) Whether

DMP does multi-pathing for native devices.

(Symantec Dynamic Multi-Pathing) The time for which an intermittently failing path needs to be monitored before DMP marks it as healthy.

(Symantec Dynamic Multi-Pathing) The default number of contiguous I/O blocks sent along a

DMP path to an array before switching to the next available path.

Tunable files for installation

Tunables value parameter definitions

186

Table B-1 Supported tunable parameters (continued)

Tunable dmp_probe_idle_lun

Description

(Symantec Dynamic Multi-Pathing) Whether the path restoration kernel thread probes idle

LUNs.

dmp_probe_threshold dmp_restore_cycles dmp_restore_interval dmp_restore_policy dmp_restore_state dmp_retry_count dmp_scsi_timeout dmp_sfg_threshold dmp_stat_interval fssmartmovethreshold

(Symantec Dynamic Multi-Pathing) The number of paths will be probed by the restore daemon.

(Symantec Dynamic Multi-Pathing) The number of cycles between running the check_all policy when the restore policy is check_periodic.

(Symantec Dynamic Multi-Pathing) The time interval in seconds the restore daemon analyzes the condition of paths.

(Symantec Dynamic Multi-Pathing) The policy used by DMP path restoration thread.

(Symantec Dynamic Multi-Pathing) Whether kernel thread for DMP path restoration is started.

(Symantec Dynamic Multi-Pathing) The number of times a path reports a path busy error consecutively before DMP marks the path as failed.

(Symantec Dynamic Multi-Pathing) The timeout value for any SCSI command sent via

DMP.

(Symantec Dynamic Multi-Pathing) The status of the subpaths failover group (SFG) feature.

(Symantec Dynamic Multi-Pathing) The time interval between gathering DMP statistics.

(Veritas Volume Manager) The file system usage threshold for SmartMove (percent). This tunable must be set after Veritas Volume

Manager is started.

Tunable files for installation

Tunables value parameter definitions

187

Table B-1

Tunable max_diskq read_ahead read_nstream read_pref_io

Supported tunable parameters (continued) reclaim_on_delete_start_time reclaim_on_delete_wait_period

Description

(Veritas File System) Specifies the maximum disk queue generated by a single file. The installer can only set the system default value of max_diskq. Refer to the tunefstab(4) manual page for setting this tunable for a specified block device.

(Veritas File System) The 0 value disables read ahead functionality, the 1 value (default) retains traditional sequential read ahead behavior, and the 2 value enables enhanced read ahead for all reads. The installer can only set the system default value of read_ahead.

Refer to the tunefstab(4) manual page for setting this tunable for a specified block device.

(Veritas File System) The number of parallel read requests of size read_pref_io that can be outstanding at one time. The installer can only set the system default value of read_nstream.

Refer to the tunefstab(4) manual page for setting this tunable for a specified block device.

(Veritas File System) The preferred read request size. The installer can only set the system default value of read_pref_io. Refer to the tunefstab(4) manual page for setting this tunable for a specified block device.

(Veritas Volume Manager) Time of day to start reclamation for deleted volumes. This tunable must be set after Veritas Volume Manager is started.

(Veritas Volume Manager) Days to wait before starting reclamation for deleted volumes. This tunable must be set after Veritas Volume

Manager is started.

Tunable files for installation

Tunables value parameter definitions

188

Table B-1 sharedminorstart

Supported tunable parameters (continued)

Tunable same_key_for_alldgs

Description

(Veritas Volume Manager) Use the same fencing key for all disk groups. This tunable must be set after Veritas Volume Manager is started.

(Veritas Volume Manager) Start of range to use for minor numbers for shared disk groups.

This tunable must be set after Veritas Volume

Manager is started.

storage_connectivity usefssmartmove vol_checkpt_default vol_cmpres_enabled vol_cmpres_threads vol_default_iodelay vol_fmr_logsz vol_max_adminio_poolsz vol_max_nmpool_sz

(Veritas Volume Manager) The CVM storage connectivity type. This tunable must be set after Veritas Volume Manager is started.

(Veritas Volume Manager) Configure

SmartMove feature (all, thinonly, none). This tunable must be set after Veritas Volume

Manager is started.

(Veritas File System) Size of VxVM storage checkpoints (kBytes). This tunable requires a system reboot to take effect.

(Veritas Volume Manager) Allow enabling compression for Volume Replicator.

(Veritas Volume Manager) Maximum number of compression threads for Volume Replicator.

(Veritas Volume Manager) Time to pause between I/O requests from VxVM utilities

(10ms units). This tunable requires a system reboot to take effect.

(Veritas Volume Manager) Maximum size of bitmap Fast Mirror Resync uses to track changed blocks (KBytes). This tunable requires a system reboot to take effect.

(Veritas Volume Manager) Maximum amount of memory used by VxVM admin I/O's (bytes).

This tunable requires a system reboot to take effect.

(Veritas Volume Manager) Maximum name pool size (bytes).

Tunable files for installation

Tunables value parameter definitions

189

Table B-1

Tunable vol_max_rdback_sz

Supported tunable parameters (continued) vol_max_wrspool_sz

Description

(Veritas Volume Manager) Storage Record readback pool maximum (bytes).

(Veritas Volume Manager) Maximum memory

.

used in clustered version of Volume Replicator vol_maxio vol_maxioctl vol_maxparallelio vol_maxspecialio vol_min_lowmem_sz vol_nm_hb_timeout vol_rvio_maxpool_sz vol_stats_enable vol_subdisk_num voldrl_max_drtregs

(Veritas Volume Manager) Maximum size of logical VxVM I/O operations (kBytes). This tunable requires a system reboot to take effect.

(Veritas Volume Manager) Maximum size of data passed into the VxVM ioctl calls (bytes).

This tunable requires a system reboot to take effect.

(Veritas Volume Manager) Number of I/O operations vxconfigd can request at one time.

This tunable requires a system reboot to take effect.

(Veritas Volume Manager) Maximum size of a VxVM I/O operation issued by an ioctl call

(kBytes). This tunable requires a system reboot to take effect.

(Veritas Volume Manager) Low water mark for memory (bytes).

(Veritas Volume Manager) Volume Replicator timeout value (ticks).

(Veritas Volume Manager) Maximum memory requested by Volume Replicator (bytes).

(Veritas Volume Manager) Enable VxVM I/O stat collection.

(Veritas Volume Manager) Maximum number of subdisks attached to a single VxVM plex.

This tunable requires a system reboot to take effect.

(Veritas Volume Manager) Maximum number of dirty VxVM regions. This tunable requires a system reboot to take effect.

Tunable files for installation

Tunables value parameter definitions

190

Table B-1 Supported tunable parameters (continued)

Tunable voldrl_max_seq_dirty

Description

(Veritas Volume Manager) Maximum number of dirty regions in sequential mode. This tunable requires a system reboot to take effect.

voldrl_min_regionsz voldrl_volumemax_drtregs voldrl_volumemax_drtregs_20 voldrl_dirty_regions voliomem_chunk_size voliomem_maxpool_sz voliot_errbuf_dflt voliot_iobuf_default voliot_iobuf_limit voliot_iobuf_max voliot_max_open

(Veritas Volume Manager) Minimum size of a

VxVM Dirty Region Logging (DRL) region

(kBytes). This tunable requires a system reboot to take effect.

(Veritas Volume Manager) Max per volume dirty regions in log-plex DRL.

(Veritas Volume Manager) Max per volume dirty regions in DCO version 20.

(Veritas Volume Manager) Number of regions cached for DCO version 30.

(Veritas Volume Manager) Size of VxVM memory allocation requests (bytes). This tunable requires a system reboot to take effect.

(Veritas Volume Manager) Maximum amount of memory used by VxVM (bytes). This tunable requires a system reboot to take effect.

(Veritas Volume Manager) Size of a VxVM error trace buffer (bytes). This tunable requires a system reboot to take effect.

(Veritas Volume Manager) Default size of a

VxVM I/O trace buffer (bytes). This tunable requires a system reboot to take effect.

(Veritas Volume Manager) Maximum total size of all VxVM I/O trace buffers (bytes). This tunable requires a system reboot to take effect.

(Veritas Volume Manager) Maximum size of a VxVM I/O trace buffer (bytes). This tunable requires a system reboot to take effect.

(Veritas Volume Manager) Maximum number of VxVM trace channels available for vxtrace commands. This tunable requires a system reboot to take effect.

Tunable files for installation

Tunables value parameter definitions

191

Table B-1 Supported tunable parameters (continued)

Tunable volpagemod_max_memsz

Description

(Veritas Volume Manager) Maximum paging module memory used by Instant Snapshots

(Kbytes).

volraid_rsrtransmax vxfs_mbuf vxfs_ninode write_nstream write_pref_io

(Veritas Volume Manager) Maximum number of VxVM RAID-5 transient reconstruct operations in parallel. This tunable requires a system reboot to take effect.

(Veritas File System) Maximum memory used for VxFS buffer cache. This tunable requires a system reboot to take effect.

(Veritas File System) Number of entries in the

VxFS inode table. This tunable requires a system reboot to take effect.

(Veritas File System) The number of parallel write requests of size write_pref_io that can be outstanding at one time. The installer can only set the system default value of write_nstream. Refer to the tunefstab(4) manual page for setting this tunable for a specified block device.

(Veritas File System) The preferred write request size. The installer can only set the system default value of write_pref_io. Refer to the tunefstab(4) manual page for setting this tunable for a specified block device.

Appendix

C

Configuring the secure shell or the remote shell for communications

This appendix includes the following topics:

About configuring secure shell or remote shell communication modes before installing products

Manually configuring passwordless ssh

Setting up ssh and rsh connection using the installer -comsetup command

Setting up ssh and rsh connection using the pwdutil.pl utility

Restarting the ssh session

Enabling rsh for Linux

About configuring secure shell or remote shell communication modes before installing products

Establishing communication between nodes is required to install Symantec software from a remote system, or to install and configure a system. The system from which the installer is run must have permissions to run rsh

(remote shell) or ssh

(secure shell) utilities. You need to run the installer with superuser privileges on the systems where you plan to install Symantec software.

You can install products to remote systems using either secure shell (ssh) or remote shell (rsh). Symantec recommends that you use ssh as it is more secure than rsh.

Configuring the secure shell or the remote shell for communications

Manually configuring passwordless ssh

193

Note: When installing on an RHEL5 / OEL5 system with SELinux enabled, only ssh is supported due to RedHat's SELinux policy restrictions.

You can set up ssh and rsh connections in many ways.

You can manually set up the SSH and RSH connection with UNIX shell commands.

You can run the installer -comsetup command to interactively set up SSH and RSH connection.

■ You can run the password utility, pwdutil.pl

.

This section contains an example of how to set up ssh password free communication.

The example sets up ssh between a source system (sys1) that contains the installation directories, and a target system (sys2). This procedure also applies to multiple target systems.

Note: The script- and web-based installers support establishing passwordless communication for you.

Manually configuring passwordless ssh

The ssh program enables you to log into and execute commands on a remote system. ssh enables encrypted communications and an authentication process between two untrusted hosts over an insecure network.

In this procedure, you first create a DSA key pair. From the key pair, you append the public key from the source system to the authorized_keys file on the target systems.

Figure C-1

illustrates this procedure.

Configuring the secure shell or the remote shell for communications

Manually configuring passwordless ssh

194

Figure C-1 Creating the DSA key pair and appending it to target systems

Source System: sys1 Target System: sys2

Private

Key

Public

Key authorized_keys file

Read the ssh documentation and online manual pages before enabling ssh. Contact your operating system support provider for issues regarding ssh configuration.

Visit the OpenSSH website that is located at: http://openssh.org

to access online manuals and other resources.

To create the DSA key pair

1 On the source system (sys1), log in as root, and navigate to the root directory.

sys1 # cd /root

2 To generate a DSA key pair on the source system, type the following command: sys1 # ssh-keygen -t dsa

System output similar to the following is displayed:

Generating public/private dsa key pair.

Enter file in which to save the key (/root/.ssh/id_dsa):

3 Press Enter to accept the default location of

/root/.ssh/id_dsa

.

Configuring the secure shell or the remote shell for communications

Manually configuring passwordless ssh

195

4 When the program asks you to enter the passphrase, press the Enter key twice.

Enter passphrase (empty for no passphrase):

Do not enter a passphrase. Press Enter.

Enter same passphrase again:

Press Enter again.

5 Output similar to the following lines appears.

Your identification has been saved in /root/.ssh/id_dsa.

Your public key has been saved in /root/.ssh/id_dsa.pub.

The key fingerprint is:

1f:00:e0:c2:9b:4e:29:b4:0b:6e:08:f8:50:de:48:d2 root@sys1

To append the public key from the source system to the authorized_keys file on the target system, using secure file transfer

1 From the source system (sys1), move the public key to a temporary file on the target system (sys2).

Use the secure file transfer program.

In this example, the file name id_dsa.pub

in the root directory is the name for the temporary file for the public key.

Use the following command for secure file transfer: sys1 # sftp sys2

If the secure file transfer is set up for the first time on this system, output similar to the following lines is displayed:

Connecting to sys2 ...

The authenticity of host 'sys2 (10.182.00.00)' can't be established. DSA key fingerprint is fb:6f:9f:61:91:9d:44:6b:87:86:ef:68:a6:fd:88:7d.

Are you sure you want to continue connecting (yes/no)?

2 Enter yes

.

Output similar to the following is displayed:

Warning: Permanently added 'sys2,10.182.00.00'

(DSA) to the list of known hosts.

root@sys2 password:

Configuring the secure shell or the remote shell for communications

Manually configuring passwordless ssh

196

3 Enter the root password of sys2.

4 At the sftp prompt, type the following command: sftp> put /root/.ssh/id_dsa.pub

The following output is displayed:

Uploading /root/.ssh/id_dsa.pub to /root/id_dsa.pub

5 To quit the SFTP session, type the following command: sftp> quit

6 Add the id_dsa.pub

keys to the authorized_keys file on the target system.

To begin the ssh session on the target system (sys2 in this example), type the following command on sys1: sys1 # ssh sys2

Enter the root password of sys2 at the prompt: password:

Type the following commands on sys2: sys2 # cat /root/id_dsa.pub >> /root/.ssh/authorized_keys sys2 # rm /root/id_dsa.pub

7 Run the following commands on the source installation system. If your ssh session has expired or terminated, you can also run these commands to renew the session. These commands bring the private key into the shell environment and make the key globally available to the user root

: sys1 # exec /usr/bin/ssh-agent $SHELL sys1 # ssh-add

Identity added: /root/.ssh/id_dsa

This shell-specific step is valid only while the shell is active. You must execute the procedure again if you close the shell during the session.

Configuring the secure shell or the remote shell for communications

Setting up ssh and rsh connection using the installer -comsetup command

197

To verify that you can connect to a target system

1 On the source system (sys1), enter the following command: sys1 # ssh -l root sys2 uname -a where sys2 is the name of the target system.

2 The command should execute from the source system (sys1) to the target system (sys2) without the system requesting a passphrase or password.

3 Repeat this procedure for each target system.

Setting up ssh and rsh connection using the installer

-comsetup command

You can interactively set up the ssh and rsh connections using the installer

-comsetup command.

Enter the following:

# ./installer -comsetup

Input the name of the systems to set up communication:

Enter the Solaris 10 Sparc system names separated by spaces:

[q,?] sys2

Set up communication for the system sys2:

Checking communication on sys2 ................... Failed

CPI ERROR V-9-20-1303 ssh permission was denied on sys2. rsh permission was denied on sys2. Either ssh or rsh is required to be set up and ensure that it is working properly between the local node and sys2 for communication

Either ssh or rsh needs to be set up between the local system and sys2 for communication

Would you like the installer to setup ssh or rsh communication automatically between the systems?

Superuser passwords for the systems will be asked. [y,n,q,?] (y) y

Enter the superuser password for system sys2:

1) Setup ssh between the systems

Configuring the secure shell or the remote shell for communications

Setting up ssh and rsh connection using the pwdutil.pl utility

198

2) Setup rsh between the systems b) Back to previous menu

Select the communication method [1-2,b,q,?] (1) 1

Setting up communication between systems. Please wait.

Re-verifying systems.

Checking communication on sys2 ..................... Done

Successfully set up communication for the system sys2

Setting up ssh and rsh connection using the pwdutil.pl

utility

The password utility, pwdutil.pl

, is bundled in the 6.2 release under the scripts directory. The users can run the utility in their script to set up the ssh and rsh connection automatically.

# ./pwdutil.pl -h

Usage:

Command syntax with simple format: pwdutil.pl check|configure|unconfigure ssh|rsh <hostname|IP addr>

[<user>] [<password>] [<port>]

Command syntax with advanced format: pwdutil.pl [--action|-a 'check|configure|unconfigure']

[--type|-t 'ssh|rsh']

[--user|-u '<user>']

[--password|-p '<password>']

[--port|-P '<port>']

[--hostfile|-f '<hostfile>']

[--keyfile|-k '<keyfile>']

[-debug|-d]

<host_URI> pwdutil.pl -h | -?

Configuring the secure shell or the remote shell for communications

Setting up ssh and rsh connection using the pwdutil.pl utility

199

Table C-1 Options with pwdutil.pl utility

Option

--action|-a 'check|configure|unconfigure'

Usage

Specifies action type, default is 'check'.

--type|-t 'ssh|rsh'

--user|-u '<user>'

--password|-p '<password>'

--port|-P '<port>'

--keyfile|-k '<keyfile>'

--hostfile|-f '<hostfile>'

-debug

-h|-?

<host_URI>

Specifies connection type, default is 'ssh'.

Specifies user id, default is the local user id.

Specifies user password, default is the user id.

Specifies port number for ssh connection, default is 22

Specifies the private key file.

Specifies the file which list the hosts.

Prints debug information.

Prints help messages.

Can be in the following formats:

<hostname>

<user>:<password>@<hostname>

<user>:<password>@<hostname>:

<port>

You can check, configure, and unconfigure ssh or rsh using the pwdutil.pl

utility.

For example:

■ To check ssh connection for only one host: pwdutil.pl check ssh hostname

■ To configure ssh for only one host: pwdutil.pl configure ssh hostname user password

■ To unconfigure rsh for only one host: pwdutil.pl unconfigure rsh hostname

■ To configure ssh for multiple hosts with same user ID and password:

Configuring the secure shell or the remote shell for communications

Setting up ssh and rsh connection using the pwdutil.pl utility

200 pwdutil.pl -a configure -t ssh -u user -p password hostname1 hostname2 hostname3

■ To configure ssh or rsh for different hosts with different user ID and password: pwdutil.pl -a configure -t ssh user1:password1@hostname1 user2:password2@hostname2

■ To check or configure ssh or rsh for multiple hosts with one configuration file: pwdutil.pl -a configure -t ssh --hostfile /tmp/sshrsh_hostfile

■ To keep the host configuration file secret, you can use the 3rd party utility to encrypt and decrypt the host file with password.

For example:

### run openssl to encrypt the host file in base64 format

# openssl aes-256-cbc -a -salt -in /hostfile -out /hostfile.enc

enter aes-256-cbc encryption password: <password>

Verifying - enter aes-256-cbc encryption password: <password>

### remove the original plain text file

# rm /hostfile

### run openssl to decrypt the encrypted host file

# pwdutil.pl -a configure -t ssh `openssl aes-256-cbc -d -a

-in /hostfile.enc` enter aes-256-cbc decryption password: <password>

■ To use the ssh authentication keys which are not under the default $

HOME/.ssh

directory, you can use --keyfile option to specify the ssh keys. For example:

### create a directory to host the key pairs:

# mkdir /keystore

### generate private and public key pair under the directory:

# ssh-keygen -t rsa -f /keystore/id_rsa

### setup ssh connection with the new generated key pair under the directory:

# pwdutil.pl -a configure -t ssh --keyfile /keystore/id_rsa user:password@hostname

You can see the contents of the configuration file by using the following command:

Configuring the secure shell or the remote shell for communications

Restarting the ssh session

201

# cat /tmp/sshrsh_hostfile user1:password1@hostname1 user2:password2@hostname2 user3:password3@hostname3 user4:password4@hostname4

# all default: check ssh connection with local user hostname5

The following exit values are returned:

2

3

0

1

Successful completion.

Command syntax error.

Ssh or rsh binaries do not exist.

Ssh or rsh service is down on the remote machine.

4

5

Ssh or rsh command execution is denied due to password is required.

Invalid password is provided.

255 Other unknown error.

Restarting the ssh session

After you complete this procedure, ssh can be restarted in any of the following scenarios:

After a terminal session is closed

After a new terminal session is opened

After a system is restarted

After too much time has elapsed, to refresh ssh

To restart ssh

1 On the source installation system (sys1), bring the private key into the shell environment.

sys1 # exec /usr/bin/ssh-agent $SHELL

2 Make the key globally available for the user root sys1 # ssh-add

Enabling rsh for Linux

The following section describes how to enable remote shell.

Configuring the secure shell or the remote shell for communications

Enabling rsh for Linux

202

Symantec recommends configuring a secure shell environment for Symantec product installations.

See

“Manually configuring passwordless ssh”

on page 193.

See the operating system documentation for more information on configuring remote shell.

To enable rsh for rhel6/sles

1 To ensure that the rsh and rsh-server

RPMs are installed, type the following command:

# rpm -qa | grep -i rsh

If it is not already in the file, type the following command to append the line

" rsh " to the /etc/securetty file:

# echo "rsh" >> /etc/securetty

2 Modify the line disable = no in the /etc/xinetd.d/rsh file.

3 In the /etc/pam.d/rsh file, change the " auth " type from " required " to

" sufficient ": auth sufficient

4 Add the "promiscuous" flag into /etc/pam.d/rsh and /etc/pam.d/rlogin after item

“pam_rhosts_auth.so”.

5 To enable the rsh server, type the following command:

# chkconfig rsh on

6 Modify the .rhosts

file. Each line of the .rhosts

file contains a fully qualified domain name or IP address for each remote system. This file also contains the name of a user having access to the local system. For example, if the root user must remotely access sys1 from sys2 , add an entry for sys2.companyname.com

to the .rhosts

file on sys1 by typing the following command:

# echo "sys2.companyname.com" >> $HOME/.rhosts

7 Install the Symantec product.

Configuring the secure shell or the remote shell for communications

Enabling rsh for Linux

203

To disable rsh for rhel6/sles

1 Remove the " rsh " entry in the /etc/securetty file.

2 Disable the rsh server by typing the following command:

# chkconfig rsh off

3 After you complete an installation procedure, delete the

.rhosts

file from each user’s

$HOME directory to ensure security:

# rm -f $HOME/.rhosts

To enable rsh for rhel7

◆ Run the following commands to enable rsh passwordless connection:

# systemctl start rsh.socket

# systemctl start rlogin.socket

# systemctl enable rsh.socket

# systemctl enable rlogin.socket

# echo rsh >> /etc/securetty

# echo rlogin >> /etc/securetty

# echo “+ +” >> /root/.rhosts

To disable rsh for rhel7

◆ Run the following commands to disable rsh passwordless connection:

# systemctl stop rsh.socket

# systemctl stop rlogin.socket

# systemctl disable rsh.socket

# systemctl disable rlogin.socket

Appendix

D

Storage Foundation components

This appendix includes the following topics:

Storage Foundation installation RPMs

Symantec Storage Foundation obsolete and reorganized installation RPMs

Storage Foundation installation RPMs

Table D-1

shows the RPM name and contents for each English language RPM for

Storage Foundation. The table also gives you guidelines for which RPMs to install based whether you want the minimum, recommended, or advanced configuration.

When you install all Storage Foundation and Symantec Cluster Server (VCS) RPMs, the combined functionality is called Storage Foundation and High Availability.

Table D-1 Storage Foundation RPMs

RPMs

VRTSaslapm

VRTSperl

Contents Configuration

Array Support Library (ASL) and Array

Policy Module(APM) binaries

Minimum

Required for the support and compatibility of various storage arrays.

Perl 5.16.1 for Veritas Minimum

Storage Foundation components

Storage Foundation installation RPMs

205

Table D-1

RPMs

VRTSvlic

VRTSvxfs

VRTSvxvm

VRTSdbed

VRTSob

VRTSodm

Storage Foundation RPMs (continued)

Contents Configuration

Symantec License Utilities

Installs the license key layout files required to decode the Storage

Foundation license keys. Provides the standard license key utilities vxlicrep, vxlicinst, and vxlictest.

Minimum

Veritas File System binaries

Required for VxFS file system support.

Minimum

Veritas Volume Manager binaries, scripts, and utilities. Required for VxVM volume manager support.

Minimum

Storage Management Software for

Databases

Recommended

Veritas Enterprise Administrator

Service

Recommended

Veritas Extension for Oracle Disk

Manager

Veritas Extension for Oracle Disk

Manager is a custom storage interface designed specifically for Oracle. Oracle

Disk Manager enables Oracle to improve performance and manage system bandwidth.

Recommended

Storage Foundation components

Storage Foundation installation RPMs

206

Table D-1

RPMs

VRTSsfcpi62

VRTSsfmh

VRTSspt

VRTSfsadv

VRTSfssdk

Storage Foundation RPMs (continued)

Contents Configuration

Symantec Storage Foundation Installer Minimum

The Storage Foundation Common

Product installer RPM contains the installer libraries and product scripts that perform the following:

■ installation configuration upgrade uninstallation adding nodes etc.

You can use these script to simplify the native operating system installations, configurations, and upgrades.

Veritas Operations Manager Managed

Host.

Recommended

Discovers configuration information on a Storage Foundation managed host.

If you want a central server to manage and monitor this managed host, download and install the VRTSsfmcs

RPM on a server, and add this managed host to the Central Server.

The VRTSsfmcs RPM is not part of this release. You can download it separately from: http://www.symantec.com/ veritas-operations-manager

Veritas Software Support Tools

Veritas File System Advanced

Recommended

Minimum

Veritas File System Software

Developer Kit

For VxFS APIs, the RPM contains the public Software Developer Kit

(headers, libraries, and sample code).

It is required if some user programs use VxFS APIs.

All

Storage Foundation components

Symantec Storage Foundation obsolete and reorganized installation RPMs

207

Symantec Storage Foundation obsolete and reorganized installation RPMs

Table D-2

lists the RPMs that are obsolete or reorganized for Storage Foundation.

Table D-2 Symantec Storage Foundation obsolete and reorganized RPMs

RPM

Obsolete and reorganized for 6.2

Description

VRTSat

VRTSatClient

VRTSatServer

Obsolete and reorganized for 5.1

Infrastructure

SYMClma

VRTSaa

VRTSccg

VRTSdbms3

VRTSicsco

VRTSjre

VRTSjre15

VRTSmh

VRTSobc33

VRTSobweb

VRTSobgui

VRTSpbx

VRTSsfm

VRTSweb

Product RPMs

Obsolete

Obsolete

Obsolete

Obsolete

Included in VRTSsfmh

Included in VRTSsfmh

Obsolete

Obsolete

Obsolete

Obsolete

Included in VRTSsfmh

Obsolete

Obsolete

Obsolete

Obsolete

Obsolete

Obsolete

Storage Foundation components

Symantec Storage Foundation obsolete and reorganized installation RPMs

208

Table D-2

RPM

VRTSacclib

VRTSalloc

VRTScmccc

VRTScmcm

VRTScmcs

VRTScscm

VRTScscw

VRTScsocw

VRTScssim

VRTScutil

VRTSd2gui-common

VRTSdb2ed-common

VRTSdbcom-common

VRTSdbed-common

VRTSdcli

VRTSddlpr

VRTSlvmconv

VRTSdsa

VRTSfsman

Symantec Storage Foundation obsolete and reorganized RPMs

(continued)

Description

Obsolete

The following information is for installations, upgrades, and uninstallations using the scriptor web-based installer.

For fresh installations VRTSacclib is not installed.

For upgrades, VRTSacclib is not uninstalled.

For uninstallation, VRTSacclib is not uninstalled.

Obsolete

Obsolete

Obsolete

Obsolete

Obsolete

Obsolete

Obsolete

Obsolete

Obsolete

Included in VRTSdbed

Included in VRTSdbed

Included in VRTSdbed

Included in VRTSdbed

Obsolete

Obsolete

Included in VRTSvxvm

Obsolete

Included in the product's main RPM.

Storage Foundation components

Symantec Storage Foundation obsolete and reorganized installation RPMs

209

Table D-2

RPM

VRTSfsmnd

VRTSfspro

VRTSmapro-common

VRTSodm-common

VRTSodm-platform

VRTSorgui-common

VRTSvcsdb

VRTSvcsmn

VRTSvcsor

VRTSvcsvr

VRTSvdid

VRTSvmman

VRTSvmpro

VRTSvrpro

VRTSvrw

VRTSvxfs-common

VRTSvxfs-platform

VRTSvxmsa

VRTSvxvm-common

VRTSvxvm-platform

Symantec Storage Foundation obsolete and reorganized RPMs

(continued)

Description

Included in the product's main RPM.

Included in VRTSsfmh

Included in VRTSsfmh

Included in VRTSodm

Included in VRTSodm

Obsolete

Included in VRTSvcsea

Included in VRTSvcs

Included in VRTSvcsea

Included in VRTSvcs

Obsolete

Included in the product's main RPM.

Included in VRTSsfmh

Included in VRTSob

Obsolete

Included in VRTSvxfs

Included in VRTSvxfs

Obsolete

Included in VRTSvxvm

Included in VRTSvxvm

Appendix

E

Troubleshooting installation issues

This appendix includes the following topics:

Restarting the installer after a failed connection

What to do if you see a licensing reminder

About the VRTSspt RPM troubleshooting tools

Incorrect permissions for root on remote system

Inaccessible system

Upgrading Symantec Storage Foundation for Databases (SFDB) tools from

5.0.x to 6.2 (2184482)

Troubleshooting the webinstaller

Restarting the installer after a failed connection

If an installation is killed because of a failed connection, you can restart the installer to resume the installation. The installer detects the existing installation. The installer prompts you whether you want to resume the installation. If you resume the installation, the installation proceeds from the point where the installation failed.

What to do if you see a licensing reminder

In this release, you can install without a license key. In order to comply with the

End User License Agreement, you must either install a license key or make the host managed by a Management Server. If you do not comply with these terms within 60 days, the following warning messages result:

Troubleshooting installation issues

About the VRTSspt RPM troubleshooting tools

211

WARNING V-365-1-1 This host is not entitled to run Symantec Storage

Foundation/Symantec Cluster Server.As set forth in the End User

License Agreement (EULA) you must complete one of the two options set forth below. To comply with this condition of the EULA and stop logging of this message, you have <nn> days to either:

- make this host managed by a Management Server (see http://go.symantec.com/sfhakeyless for details and free download), or

- add a valid license key matching the functionality in use on this host using the command 'vxlicinst' and validate using the command

'vxkeyless set NONE'.

To comply with the terms of the EULA, and remove these messages, you must do one of the following within 60 days:

■ Install a valid license key corresponding to the functionality in use on the host.

See

“Installing Symantec product license keys”

on page 33.

After you install the license key, you must validate the license key using the following command:

# /opt/VRTS/bin/vxlicrep

■ Continue with keyless licensing by managing the server or cluster with a management server.

For more information about keyless licensing, see the following URL: http://go.symantec.com/sfhakeyless

About the VRTSspt RPM troubleshooting tools

The VRTSspt RPM provides a group of tools for troubleshooting a system and collecting information on its configuration. If you install and use the VRTSspt RPM, it will be easier for Symantec Support to diagnose any issues you may have.

The tools can gather Veritas File System and Veritas Volume Manager metadata information and establish various benchmarks to measure file system and volume manager performance. Although the tools are not required for the operation of any

Symantec product, Symantec recommends installing them should a support case be needed to be opened with Symantec Support. Use caution when you use the

VRTSspt RPM, and always use it in concert with Symantec Support.

Troubleshooting installation issues

Incorrect permissions for root on remote system

212

Incorrect permissions for root on remote system

The permissions are inappropriate. Make sure you have remote root access permission on each system to which you are installing.

Failed to setup rsh communication on 10.198.89.241:

'rsh 10.198.89.241 <command>' failed

Trying to setup ssh communication on 10.198.89.241.

Failed to setup ssh communication on 10.198.89.241:

Login denied

Failed to login to remote system(s) 10.198.89.241.

Please make sure the password(s) are correct and superuser(root) can login to the remote system(s) with the password(s).

If you want to setup rsh on remote system(s), please make sure rsh with command argument ('rsh <host> <command>') is not denied by remote system(s).

Either ssh or rsh is needed to be setup between the local node and 10.198.89.241 for communication

Would you like the installer to setup ssh/rsh communication automatically between the nodes?

Superuser passwords for the systems will be asked. [y,n,q] (y) n

System verification did not complete successfully

The following errors were discovered on the systems:

The ssh permission denied on 10.198.89.241

rsh exited 1 on 10.198.89.241

either ssh or rsh is needed to be setup between the local node and 10.198.89.241 for communication

Suggested solution: You need to set up the systems to allow remote access using ssh or rsh .

See

“About configuring secure shell or remote shell communication modes before installing products”

on page 192.

Note: Remove remote shell permissions after completing the SF installation and configuration.

Troubleshooting installation issues

Inaccessible system

213

Inaccessible system

The system you specified is not accessible. This could be for a variety of reasons such as, the system name was entered incorrectly or the system is not available over the network.

Verifying systems: 12% ....................................

Estimated time remaining: 0:10 1 of 8

Checking system communication .............................. Done

System verification did not complete successfully

The following errors were discovered on the systems: cannot resolve hostname host1

Enter the Linux system names separated by spaces: q,? (host1)

Suggested solution: Verify that you entered the system name correctly; use the ping (1M) command to verify the accessibility of the host.

Upgrading Symantec Storage Foundation for

Databases (SFDB) tools from 5.0.x to 6.2 (2184482)

The sfua_rept_migrate command results in an error message after upgrading

SFHA or SF for Oracle RAC version 5.0 to SFHA or SF for Oracle RAC 6.2.

When upgrading from SF version 5.0 to SF 6.2 the S*vxdbms3 startup script is renamed to NO_S*vxdbms3. The S*vxdbms3 startup script is required by sfua_rept_upgrade . Thus when sfua_rept_upgrade is run, it is unable to find the

S*vxdbms3 startup script and gives the error message:

/sbin/rc3.d/S*vxdbms3 not found

SFORA sfua_rept_migrate ERROR V-81-3558 File: is missing.

SFORA sfua_rept_migrate ERROR V-81-9160 Failed to mount repository.

Workaround: Before running sfua_rept_migrate , rename the startup script

NO_S*vxdbms3 to S*vxdbms3.

Troubleshooting the webinstaller

This section provides possible solutions to problems that may occur when using the webinstaller script:

Issue: The webinstaller script may report an error.

You may receive a similar error message when using the webinstaller:

Error: could not get hostname and IP address

Troubleshooting installation issues

Troubleshooting the webinstaller

214

Solution: Check whether

/etc/hosts and

/etc/resolv.conf

file are correctly configured.

Issue: The hostname is not a fully qualified domain name.

You must have a fully qualified domain name for the hostname in https://<hostname>:<port>/.

Solution: Check whether the domain section is defined in /etc/resolv.conf

file.

Issue: FireFox 3 may report an error.

You may receive a similar error message when using FireFox 3:

Certificate contains the same serial number as another certificate.

Solution: Visit FireFox knowledge base website: http://support.mozilla.com/en-US/kb/Certificate+contains+the+same+serial+number+as+another+certificate

Appendix

F

Compatability issues when installing Storage

Foundation with other products

This appendix includes the following topics:

Installing, uninstalling, or upgrading Storage Foundation products when other

Symantec products are present

Installing, uninstalling, or upgrading Storage Foundation products when VOM is already present

Installing, uninstalling, or upgrading Storage Foundation products when

NetBackup is already present

Installing, uninstalling, or upgrading Storage

Foundation products when other Symantec products are present

Installing Storage Foundation when other Symantec products are installed can create compatibility issues. For example, installing Storage Foundation products when VOM, ApplicationHA, and NetBackup are present on the systems.

Compatability issues when installing Storage Foundation with other products

Installing, uninstalling, or upgrading Storage Foundation products when VOM is already present

216

Installing, uninstalling, or upgrading Storage

Foundation products when VOM is already present

If you plan to install or upgrade Storage Foundation products on systems where

VOM has already been installed, be aware of the following compatibility issues:

■ When you install or upgrade Storage Foundation products where VOM Central

Server is present, the installer skips the VRTSsfmh upgrade and leaves the

VOM Central Server and Managed Host RPMs as is.

When uninstalling Storage Foundation products where VOM Central Server is present, the installer does not uninstall VRTSsfmh.

When you install or upgrade Storage Foundation products where VOM Managed

Host is present, the installer gives warning messages that it will upgrade

VRTSsfmh.

Installing, uninstalling, or upgrading Storage

Foundation products when NetBackup is already present

If you plan to install or upgrade Storage Foundation on systems where NetBackup has already been installed, be aware of the following compatibility issues:

■ When you install or upgrade Storage Foundation products where NetBackup is present, the installer does not uninstall VRTSpbx and VRTSicsco. It does not upgrade VRTSat.

■ When you uninstall Storage Foundation products where NetBackup is present, the installer does not uninstall VRTSpbx, VRTSicsco, and VRTSat.

Index

A about

Deployment Server 77

installation and configuration methods 26

installation preparation 36

installation using operating system-specific

methods 60

planning for installation 25

response files 27

SORT 16

Symantec product licensing 30

Veritas Operations Manager 16

web-based installer 47

assesing system

installation readiness 39

B

backup boot disk group 141 rejoining 141

before using

web-based installer 48

C checking

installation readiness 39

checking product versions 20

configuring

rsh 37 ssh 37

creating

backups 115

Install Templates 102

D defining

Install Bundles 97

deploying

Symantec product updates to your

environment 94

Symantec releases 104

deploying using

Install Bundles 104

deploying using Install Templates

Install Templates 104

deployment preferences

setting 83

Deployment Server

about 77

downloading the most recent release information

from the SORT site 85

installing 79

loading release information and patches on to 86

overview 78

proxy server 107

setting up 80

specifying a non-default repository location 85

disabling

external network connection attempts 23

disk groups

rootdg 73

disk space requirements 20 downloading maintenance releases and patches 20

downloading the most recent release information by running the Deployment Server from a system

with Internet access 85

I

Install Bundles

defining 97

deploying using the Deployment Server 104

integration options 120

Install Templates

creating 102

deploying using Install Templates 104

installation

Red Hat Satellite server 69

installer

about the script-based installer 41

installer patches

obtaining either manually or automatically 22

Index 218

Installing

SF with the web-based installer 50 web-based installer 50

installing

SF using operating system-specific methods 60

Symantec product license keys 33

the Deployment Server 79

using Kickstart 61

using response files 53

using yum 64

K keyless licensing

setting or changing the product level 31

Kickstart

installing 61

sample configuration file 62

L

licensing 24

add-on 23

CDS 24

full 23

installing Symantec product license keys 33

setting or changing the product level for keyless

licensing 31

M migrating from Storage Foundation Basic to Storage

Foundation Standard 137

mounting

software disc 38

O obtaining installer patches either automatically or

manually 22

security exception on Mozilla Firefox 49

overview

Deployment Server 78

P

planning to upgrade VVR 117

post-upgrade

updating variables 149

verifying 150

prechecking

using the installer 39

preinstallation 117

preinstallation check

web-based installer 50

preparing to upgrade 114

proxy server

connecting the Deployment Server 107

R

Red Hat Satellite server

installing 69

rejoining

backup boot disk group 141

release images

viewing or downloading available 87

release information and patches

loading using the Deployment Server 86

release notes 19

releases finding out which releases you have, and which

upgrades or updates you may need 95

removing

license files 167

the Replicated Data Set 163

Replicated Data Set

removing the 163

repository images viewing and removing repository images stored

in your repository 92

response files

about 27

installation 53

syntax 28

uninstalling 169

upgrading 132

root disk group 73

rsh

configuration 37

S script-based installer

about 41

setting

deployment preferences 83

environment variables 37

setting up

Deployment Server 80

Index 219

SF installation

preinstallation information 20

SFDB authentication 153 configuring vxdbd 153

simulataneous install or upgrade 120

specifying

non-default repository location 85

ssh

configuration 37

starting

web-based installer 48

Storage Foundation Basic to Storage Foundation

Standard

migrating 137

supported operating systems 20

Symantec product license keys

installing 33

Symantec product updates

deploying to your environment 94

Symantec products

starting process 156 stopping process 156

Symantec releases

deploying a specific release 104

T tunables file

about setting parameters 179

parameter definitions 184

preparing 183

setting for configuration 180 setting for installation 180 setting for upgrade 180

setting parameters 183

setting with no other operations 181

setting with un-integrated response file 182

U uninstalling

using response files 169

using the web-based installer 166

unsuccessful upgrade 141

upgrade

array support 120

creating backups 115

getting ready 114

methods 109

supported upgrade paths 110

upgrades or updates

finding out which releases you have 95

upgrading

using response files 132

using the web-based installer 127

upgrading VVR

from 4.1 118

planning 117

V verifying

product installation 155

viewing and removing repository images

stored in your repository 92

viewing or downloading

available release images 87

vradmin

delpri 164 stoprep 164

VVR 4.1

planning an upgrade from 118

vxplex

used to remove mirrors of root disk volumes 161

W

web-based installer 50

about 47

before using 48

installation 50 preinstallation check 50

starting 48

uninstalling 166

upgrading 127

Y yum

installing 64

advertisement

Was this manual useful for you? Yes No
Thank you for your participation!

* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project

Download PDF

advertisement

Table of contents