Veritas Storage Foundation™ 6.0.1 Installation Guide

Veritas Storage Foundation™
6.0.1 Installation Guide - AIX
February 2015
Veritas 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.0.1
Document version: 6.0.1 Rev 4
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. 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
customercare_apac@symantec.com
Europe, Middle-East, and Africa
semea@symantec.com
North America and Latin America
supportsolutions@symantec.com
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:
doc_feedback@symantec.com
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
Introducing Storage Foundation ...................................... 15
About Veritas products ..................................................................
About Storage Foundation ........................................................
About Veritas Replicator Option .................................................
About Veritas graphical user interfaces .............................................
About Veritas Operations Manager .............................................
Chapter 2
System requirements ......................................................... 17
Release notes .............................................................................
Hardware compatibility list (HCL) .....................................................
Supported operating systems ..........................................................
Disk space requirements ................................................................
Discovering product versions and various requirement
information ............................................................................
Database requirements .................................................................
Chapter 3
17
17
18
18
18
19
Planning to install SF ......................................................... 20
About planning for SF installation .....................................................
About installation and configuration methods for SF .............................
About response files ...............................................................
About the Veritas installer ...............................................................
Downloading the Storage Foundation software ...................................
Chapter 4
15
15
16
16
16
20
21
21
22
24
Licensing SF ......................................................................... 26
About Veritas product licensing ....................................................... 26
Setting or changing the product level for keyless licensing .................... 27
Installing Veritas product license keys ............................................... 29
Contents
Section 2
Installation of Storage Foundation ................... 30
Chapter 5
Preparing to install Storage Foundation ........................ 31
Installation preparation overview ......................................................
About using ssh or rsh with the Veritas installer ..................................
Setting environment variables .........................................................
Mounting the product disc ..............................................................
Assessing the system for installation readiness ..................................
About Symantec Operations Readiness Tools ..............................
Prechecking your systems using the Veritas installer .....................
Chapter 6
31
32
32
33
34
35
35
Installing Storage Foundation using the
script-based installer ................................................... 37
Installing Storage Foundation using the installer ................................. 37
Chapter 7
Installing Storage Foundation using the web-based
installer ...........................................................................
About the Web-based installer ........................................................
Before using the Veritas Web-based installer .....................................
Starting the Veritas Web-based installer ............................................
Obtaining a security exception on Mozilla Firefox ................................
Performing a pre-installation check with the Veritas Web-based
installer ................................................................................
Installing SF with the Web-based installer ..........................................
Chapter 8
40
41
41
42
43
43
Performing an automated installation using
response files ................................................................. 46
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 ......................
Chapter 9
40
46
47
49
50
50
Installing Storage Foundation using operating
system-specific methods ............................................. 53
Installing SF using NIM and the installer ............................................ 53
Preparing the installation bundle on the NIM server ....................... 53
Installing SF on the NIM client using SMIT on the NIM
server ............................................................................ 54
8
Contents
Installing SF and the operating system on the NIM client using
SMIT .............................................................................
Installing Storage Foundation using the mksysb utility ..........................
Creating the mksysb backup image ............................................
Installing mksysb image on alternate disk ...................................
Verifying the installation ...........................................................
Chapter 10
55
56
56
57
59
Configuring Storage Foundation ..................................... 60
Configuring Storage Foundation using the installer ..............................
Configuring Storage Foundation manually .........................................
Configuring Veritas File System .................................................
Configuring DMP support for booting over a SAN ................................
Configuring the Storage Foundation for Databases repository database
after installation ......................................................................
60
60
61
61
64
Section 3
Upgrade of SF ................................................................ 65
Chapter 11
Planning to upgrade SF ..................................................... 66
Upgrade methods for SF ................................................................
Supported upgrade paths for SF 6.0.1 ..............................................
Preparing to upgrade SF ................................................................
Getting ready for the upgrade ...................................................
Preparing for an upgrade of Storage Foundation ...........................
Creating backups ...................................................................
Tasks for upgrading the Storage Foundation for Databases
(SFDB) ...........................................................................
Pre-upgrade tasks for migrating the SFDB repository
database ........................................................................
Pre-upgrade planning for Veritas Volume Replicator ......................
Verifying that the file systems are clean .......................................
Upgrading the array support .....................................................
Chapter 12
66
67
71
71
72
72
73
73
74
76
77
Upgrading Storage Foundation ........................................ 79
Upgrading Storage Foundation with the product installer ......................
Upgrading Storage Foundation using the Veritas Web-based
installer ................................................................................
Upgrade Storage Foundation and AIX on a DMP-enabled rootvg ...........
Upgrading from prior version of SF on AIX 6.1 to SF 6.0.1 on a
DMP-enabled rootvg .........................................................
Upgrading from a prior version of SF on AIX 5.3 to SF 6.0.1 on
AIX 6.1 or AIX 7.1 on a DMP-enabled rootvg ..........................
79
81
82
82
83
9
Contents
Upgrading from SF 6.0.1 on AIX 6.1 to SF 6.0.1 on AIX 7.1 on a
DMP-enabled rootvg ........................................................
Upgrading using SMIT ...................................................................
Upgrading the AIX operating system ................................................
Upgrading Veritas Volume Replicator ................................................
Upgrading VVR without disrupting replication ...............................
Chapter 13
84
85
86
87
87
Performing an automated SF upgrade using
response files ................................................................. 90
Upgrading SF using response files ................................................... 90
Response file variables to upgrade Storage Foundation ....................... 91
Sample response file for SF upgrade ................................................ 92
Chapter 14
Upgrading SF using an alternate disk ............................. 93
About upgrading SF using an alternate disk .......................................
Supported upgrade scenarios .........................................................
Supported upgrade paths for SF using alternate disks ..........................
Preparing to upgrade SF on an alternate disk .....................................
Upgrading SF on an alternate disk ...................................................
Verifying the upgrade ....................................................................
Chapter 15
93
94
94
94
96
98
Upgrading SF using Network Install Manager
Alternate Disk Migration ............................................. 99
Supported upgrade paths for SF using NIM ADM ................................ 99
Preparing to upgrade SF and the operating system using the nimadm
utility .................................................................................. 100
Preparing the installation bundle on the NIM server ........................... 100
Upgrading SF and the operating system using the nimadm utility .......... 102
Verifying the upgrade performed using the NIM ADM utility .................. 104
Chapter 16
Migrating from Storage Foundation Basic to Storage
Foundation Standard .................................................. 105
Migrating from Storage Foundation Basic to Storage Foundation
Standard ............................................................................. 105
Chapter 17
Performing post-upgrade tasks ...................................... 108
Optional configuration steps ..........................................................
Post upgrade tasks for migrating the SFDB repository database ...........
Migrating from a 5.0 repository database to 6.0.1 ........................
Migrating from a 5.1 or higher repository database to 6.0.1 ............
108
109
109
112
10
Contents
After upgrading from 5.0.x and before migrating SFDB .................
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 .......................................
114
114
115
115
116
116
116
Section 4
Post-installation tasks ............................................ 117
Chapter 18
Verifying the SF installation ............................................ 118
Verifying that the products were installed .........................................
Installation log files ......................................................................
Using the installation log file ....................................................
Using the summary file ..........................................................
Starting and stopping processes for the Veritas products ....................
Checking Veritas Volume Manager processes ..................................
Checking Veritas File System installation .........................................
118
119
119
119
119
120
121
Section 5
Uninstallation of SF .................................................. 122
Chapter 19
Uninstalling Storage Foundation ................................... 123
Preparing to uninstall a SF product .................................................
Moving volumes to physical disks .............................................
Removing the Replicated Data Set .................................................
Uninstalling SF filesets using the script-based installer .......................
Uninstalling SF with the Veritas Web-based installer ..........................
Removing Storage Foundation products using SMIT ..........................
Removing the Storage Foundation for Databases (SFDB) repository
after removing the product ......................................................
Chapter 20
123
124
126
128
129
130
132
Uninstalling SF using response files ............................. 133
Uninstalling SF using response files ............................................... 133
Response file variables to uninstall Storage Foundation ...................... 134
Sample response file for SF uninstallation ........................................ 134
11
Contents
Section 6
Installation reference .............................................. 136
Appendix A
Installation scripts
............................................................ 137
Installation script options .............................................................. 137
Appendix B
Tunable files for installation ........................................... 142
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 ..............................................
Appendix C
Configuring the secure shell or the remote shell for
communications .......................................................... 154
About configuring secure shell or remote shell communication modes
before installing products ........................................................
Manually configuring and passwordless ssh .....................................
Restarting the ssh session ............................................................
Enabling rsh for AIX ....................................................................
Appendix D
142
143
144
145
146
146
147
154
155
159
159
Storage Foundation components ................................... 161
Storage Foundation installation filesets ........................................... 161
Veritas Storage Foundation obsolete and reorganized installation
filesets ................................................................................ 164
Appendix E
Troubleshooting installation issues .............................. 167
Restarting the installer after a failed connection ................................
What to do if you see a licensing reminder .......................................
Troubleshooting an installation on AIX ............................................
Incorrect permissions for root on remote system ...............................
Resource temporarily unavailable ..................................................
Inaccessible system ....................................................................
Troubleshooting the webinstaller ....................................................
167
167
168
168
169
170
171
12
Contents
Appendix F
Changing NFS server major numbers for VxVM
volumes .........................................................................
172
Changing NFS server major numbers for VxVM volumes .................... 172
Appendix G
Compatability issues when installing Storage
Foundation with other products .............................. 174
Installing, uninstalling, or upgrading Storage Foundation products when
other Veritas products are present ............................................ 174
Installing, uninstalling, or upgrading Storage Foundation products when
VOM is already present .......................................................... 175
Installing, uninstalling, or upgrading Storage Foundation products when
NetBackup is already present .................................................. 175
Index ................................................................................................................... 176
13
Section
Installation overview and
planning
■
Chapter 1. Introducing Storage Foundation
■
Chapter 2. System requirements
■
Chapter 3. Planning to install SF
■
Chapter 4. Licensing SF
1
Chapter
1
Introducing Storage
Foundation
This chapter includes the following topics:
■
About Veritas products
■
About Veritas graphical user interfaces
About Veritas products
The following products are available for this release.
About Storage Foundation
Veritas Storage Foundation by Symantec 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.
You add high availability functionality to Storage Foundation HA by installing Veritas
Cluster Server software.
VxFS and VxVM are a part of all Veritas Storage Foundation products. Do not install
or update VxFS or VxVM as individual components.
Introducing Storage Foundation
About Veritas graphical user interfaces
About Veritas Storage Foundation Basic
Storage Foundation Basic supports all Storage Foundation Standard features,
however, there are deployment and technical support limitations.
About Veritas Replicator Option
Veritas Replicator Option is an optional, separately-licensable feature.
Veritas Volume Replicator replicates data to remote locations over any standard
IP network to provide continuous data availability.
This option is available with Storage Foundation for Oracle RAC, Storage Foundation
Cluster File System, and Storage Foundation Standard and Enterprise products.
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 graphical user interfaces
The following are descriptions of Veritas GUIs.
About Veritas Operations Manager
Veritas Operations Manager provides a centralized management console for Veritas
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 at no charge at
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. Veritas Storage Foundation
Management Server is deprecated.
16
Chapter
2
System requirements
This chapter includes the following topics:
■
Release notes
■
Hardware compatibility list (HCL)
■
Supported operating systems
■
Disk space requirements
■
Discovering product versions and various requirement information
■
Database requirements
Release notes
The Release Notes for each Veritas 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
Hardware compatibility list (HCL)
The hardware compatibility list contains information about supported hardware and
is updated regularly. Before installing or upgrading Storage Foundation and High
Availability Solutions products, review the current compatibility list to confirm the
compatibility of your hardware and software.
For the latest information on supported hardware, visit the following URL:
System requirements
Supported operating systems
http://www.symantec.com/docs/TECH170013
For information on specific High Availability setup requirements, see the Veritas
Cluster Server Installation Guide.
Supported operating systems
For information on supported operating systems, see the Storage Foundation
Release Notes.
Disk space requirements
Before installing your products, confirm that your system has enough free disk
space.
Use the Perform a Pre-installation 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 Veritas installer” on page 22.
Discovering product versions and various requirement
information
Symantec provides several methods to check the Veritas product you have installed,
plus various requirement information.
You can check the existing product versions using the installer command with
the -version option before or after you install. After you have installed the current
version of the product, you can use the showversion script in the /opt/VRTS/install
directory to find version information.
The information that the version option or the showversion script discovers on
systems includes the following:
■
The installed version of all released Storage Foundation and High Availability
Suite of products
■
The required filesets or patches (if applicable) that are missing
■
The available updates (including patches or hotfixes) from Symantec Operations
Readiness Tools (SORT) for the installed products
18
System requirements
Database requirements
To run the version checker
1
Mount the media.
2
Start the installer with the -version option.
# ./installer -version system1 system2
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, DB2, and Sybase on VxFS and VxVM.
SF does not support running SFDB tools with DB2 and Oracle.
19
Chapter
3
Planning to install SF
This chapter includes the following topics:
■
About planning for SF installation
■
About installation and configuration methods for SF
■
About the Veritas installer
■
Downloading the Storage Foundation software
About planning for SF installation
Before you continue, make sure that you are using the current version of this guide.
The latest documentation is available on the Symantec Symantec Operations
Readiness Tools (SORT) website.
https://sort.symantec.com/documents
Document version: 6.0.1 Rev 4.
This installation guide is designed for system administrators who already have a
knowledge of basic UNIX system and network administration. Basic knowledge
includes commands such as tar, mkdir, and simple shell scripting. Also required
is basic familiarity with the specific platform and operating system where SF will be
installed.
Follow the preinstallation instructions if you are installing Storage Foundation.
The following Veritas Storage Foundation products by Symantec are installed with
these instructions:
■
Veritas Storage Foundation Basic
■
Veritas Storage Foundation (Standard and Enterprise Editions)
Several component products are bundled with each of these SF products.
Planning to install SF
About installation and configuration methods for SF
About installation and configuration methods for SF
You can install and configure SF using Veritas installation programs or using native
operating system methods.
Use one of the following methods to install and configure SF:
■
The Veritas product installer
The installer displays a menu that simplifies the selection of installation options.
■
The product-specific installation scripts
The installation scripts provide a command-line interface to install a specific
product. The product-specific scripts enable you to specify some additional
command-line options. Installing with the installation script is also the same as
specifying SF from the installer menu.
■
The Web-based Veritas installer
The installer provides an interface to manage the installation from a remote site
using a standard Web browser.
See “About the Web-based installer” on page 40.
■
Silent installation with response files
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 to install silently on one or more systems.
See “About response files” on page 21.
■
Network Installation Manager (NIM)
You can use the Veritas product installer or the product-specific installation
script to generate a NIM configuration file. Use the generated script to install
Veritas filesets from your NIM server.
About response files
The installer or product installation script generates a response file during any
installation, configuration, upgrade (except rolling 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.
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.
21
Planning to install SF
About the Veritas installer
See “Installation script options” on page 137.
Syntax in the response file
The syntax of the Perl statements that are 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", "value", "value"];
About the Veritas installer
To install your Veritas product, use one of the following methods:
■
The general product installer. The general product installer enables you to install
and configure the product, verify preinstallation requirements, and view the
product’s description. You perform the installation from a disc, and you are
prompted to choose a product to install.
See “Installing Storage Foundation using the installer” on page 37.
■
Product-specific installation scripts. If you obtained a standalone Veritas product
from an electronic download site, the single product download files do not contain
the general product installer. Use the product installation script to install the
individual products. You can find these scripts at the root of the product media
in the scripts directory. These scripts are also installed with the product.
Table 3-1 lists all the SFHA Solutions product installation scripts. The list of product
installation scripts that you find on your system depends on the product that you
install on your system.
Note: The name of the script is different depending on whether you run the script
from the install media or from a system on which the product software is installed.
22
Planning to install SF
About the Veritas installer
Table 3-1
Product installation scripts
Veritas product name
Product installation script Product installation script
(When running the script (When running the script
from the install media)
from a system on which
the SFHA Solutions
product is installed)
Veritas Cluster Server (VCS) installvcs
installvcs<version>
Veritas Storage Foundation
(SF)
installsf<version>
installsf
Veritas Storage Foundation installsfha
and High Availability (SFHA)
installsfha<version>
Veritas Storage Foundation
Cluster File System High
Availability (SFCFSHA)
installsfcfsha
installsfcfsha<version>
Veritas Storage Foundation
for Oracle RAC (SF Oracle
RAC)
installsfrac
installsfrac<version>
Veritas Dynamic
Multi-Pathing
installdmp
installdmp<version>
The scripts that are installed on the system include the product version in the script
name. For example, to install the SF script from the install media, run the installsf
command. However, to run the script from the installed binaries, run the
installsf<version> command.
For example, for the 6.0.1 version:
# /opt/VRTS/install/installsf601 -configure
Note: Do not include the release version if you use the general product installer to
install the product.
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 Control+c to stop and exit the program if an installation procedure hangs.
After a short delay, the script exits.
23
Planning to install SF
Downloading the Storage Foundation software
■
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 137.
Downloading the Storage Foundation software
One method of obtaining the Storage Foundation software is to download it to your
local system from the Symantec Web site.
For a Trialware download, perform the following. Contact your Veritas 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 & Downloads link.
3
On the next page near the bottom of the page, click Business Continuity.
4
Under Cluster Server, click Download Now.
5
In the new window, click Download Now.
6
Review the terms and conditions, and click I agree.
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 Veritas 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 Veritas installer” on page 22.
24
Planning to install SF
Downloading the Storage Foundation software
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 4 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 18.
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 Veritas 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.
25
Chapter
4
Licensing SF
This chapter includes the following topics:
■
About Veritas product licensing
■
Setting or changing the product level for keyless licensing
■
Installing Veritas product license keys
About Veritas product licensing
You have the option to install Veritas 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.
www.symantec.com/techsupp/
The Veritas 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.
The installer prompts for the product modes and options that you want to install,
and then sets the required product level.
Licensing SF
Setting or changing the product level for keyless licensing
Within 60 days of choosing this option, you must install a valid license key
corresponding to the license level entitled. 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 prior release of the Veritas 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 27.
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 Veritas product license keys” on page 29.
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: In order 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 Veritas products
and functionality that are licensed.
For more information to use keyless licensing and to download the management
server, see the following URL:
http://go.symantec.com/vom
27
Licensing SF
Setting or changing the product level for keyless licensing
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.
After you install, 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:
# cd /opt/VRTSvlic/bin
2
View the current setting for the product level.
# ./vxkeyless -v display
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 Veritas products until you install a new key
or set a new product level.
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.
28
Licensing SF
Installing Veritas product license keys
Installing Veritas product license keys
The VRTSvlic fileset enables product licensing. After the VRTSvlic is installed, the
following commands and their manual pages are available on the system:
vxlicinst
Installs a license key for a Symantec product
vxlicrep
Displays currently installed licenses
vxlictest
Retrieves features and their descriptions
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.
To install a new license
◆
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
To see a list of your vxkeyless keys, enter the following command:
# ./vxkeyless display
After you upgrade from a previous release, the output you see when you run the
vxkeyless display command includes the previous release's vxkeyless keys.
Each vxkeyless key name includes the suffix _<previous_release_version>. For
example, DMP_6.0, or SFENT_VR_5.1SP1, or VCS_GCO_5.1. During the upgrade
process, the CPI installer prompts you to update the vxkeyless keys to the current
release level. If you update the vxkeyless keys during the upgrade process, you no
longer see the _<previous_release_number> suffix after the keys are updated.
29
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. Performing an 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 Veritas 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 Veritas product licensing”
on page 26.
Download the software, or insert the product See “Downloading the Storage Foundation
DVD.
software” on page 24.
See “Mounting the product disc” on page 33.
Set environment variables.
See “Setting environment variables”
on page 32.
Preparing to install Storage Foundation
About using ssh or rsh with the Veritas installer
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 154.
Verify that hardware, software, and operating See “Release notes” on page 17.
system requirements are met.
Check that sufficient disk space is available. See “Disk space requirements” on page 18.
Use the installer to install the products.
See “About the Veritas installer” on page 22.
About using ssh or rsh with the Veritas installer
The installer uses passwordless secure shell (ssh) or remote shell (rsh)
communications among systems. The installer uses the ssh or rsh daemon that
comes bundled with the operating system. During an installation, you choose the
communication method that you want to use. You then provide the installer with
the superuser passwords for the systems where you plan to install. The ssh or rsh
communication among the systems is removed when the installation process
completes, unless the installation abruptly terminates. If installation terminated
abruptly, use the installation script's -comcleanup option to remove the ssh or rsh
configuration from the systems.
See “Installation script options” on page 137.
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:
■
When you perform installer sessions using a response file.
See “About configuring secure shell or remote shell communication modes before
installing products” on page 154.
Setting environment variables
Most of the commands used in the installation are in the /sbin or /usr/sbin
directory. Add these directories to your PATH environment variable as necessary.
After installation, SF commands are in /opt/VRTS/bin. SF manual pages are stored
in /opt/VRTS/man.
32
Preparing to install Storage Foundation
Mounting the product disc
Some VCS custom scripts reside in /opt/VRTSvcs/bin. If you are installing a high
availability product, add /opt/VRTSvcs/bin to the PATH also.
Add the following directories to your PATH and MANPATH environment variable:
■
If you are using Bourne or Korn shell (sh or ksh), enter the following:
$ PATH=$PATH:/usr/sbin:/opt/VRTS/bin
$ MANPATH=/usr/share/man:/opt/VRTS/man:$MANPATH
$ export PATH MANPATH
■
If you are using a C shell (csh or tcsh), enter the following:
% set path = ( $path /usr/sbin /opt/VRTS/bin )
% setenv MANPATH /usr/share/man:/opt/VRTS/man:$MANPATH
The nroff versions of the online manual pages are not readable using the man
command if the bos.txt.tfs fileset is not installed; however, the VRTSvxvm and
VRTSvxfs filesets install ASCII versions in the /opt/VRTS/man/cat* and
/opt/VRTS/man/man* directories that are readable without the bos.txt.tfs fileset.
Mounting the product disc
You must have superuser (root) privileges to load the SF software.
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
Determine the device access name of the disc drive. For example, enter:
# lsdev -C -c cdrom
The output resembles:
cd0 Available 1G-19-00 IDE DVD-ROM Drive
In this example, cd0 is the disc’s device access name.
33
Preparing to install Storage Foundation
Assessing the system for installation readiness
3
Make sure the /cdrom file system is created:
# cat /etc/filesystems
If the /cdrom file system exists, the output contains a listing that resembles:
.
.
/cdrom:
dev = /dev/cd0
vfs = cdrfs
mount = false
options = ro
account = false
.
.
4
If the /cdrom file system does not exist, create it:
# crfs -v cdrfs -p ro -d cd0 -m /cdrom
5
Insert the product disc with the SF software into a drive that is connected to
the system.
6
Mount the disc:
# mount /cdrom
# cd /cdrom
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 Veritas Storage Foundation 6.0.1.
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 35.
34
Preparing to install Storage Foundation
Assessing the system for installation readiness
Prechecking your systems using the installer Performs a pre-installation check on the
specified systems. The Veritas product
installer reports whether the specified
systems meet the minimum requirements for
installing Veritas Storage Foundation 6.0.1.
See “Prechecking your systems using the
Veritas installer” on page 35.
About Symantec Operations Readiness Tools
Symantec Operations Readiness Tools (SORT) is a Web site that automates and
simplifies some of the most time-consuming administrative tasks. SORT helps you
manage your datacenter more efficiently and get the most out of your Symantec
products.
Among its broad set of features, SORT lets you do the following:
■
Generate server-specific reports that describe how to prepare your servers for
installation or upgrade of Symantec enterprise products.
■
Access a single site with the latest production information, including patches,
agents, and documentation.
■
Create automatic email notifications for changes in patches, documentation,
and array-specific modules.
To access SORT, go to:
https://sort.symantec.com
Prechecking your systems using the Veritas installer
The script-based and Web-based installer's precheck option checks for the following:
■
Recommended swap space for installation
■
Recommended memory sizes on target systems for Veritas 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 installer” on page 37.
See “Installing SF with the Web-based installer” on page 43.
2
Select the precheck option:
35
Preparing to install Storage Foundation
Assessing the system for installation readiness
■
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
Review the output and make the changes that the installer recommends.
36
Chapter
6
Installing Storage
Foundation using the
script-based installer
This chapter includes the following topics:
■
Installing Storage Foundation using the installer
Installing Storage Foundation using the installer
The Veritas 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 154.
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 33.
3
Move to the top-level directory on the disc.
# cd /mnt/cdrom
Installing Storage Foundation using the script-based installer
Installing Storage Foundation using the installer
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
Enter I to install and press Return.
6
When the list of available products is displayed, select Storage Foundation,
enter the corresponding number, and press Return.
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_SF_Ux_version.pdf file present on the media? [y,n,q,?] y
8
Select from one of the following installation options:
■
Minimal filesets: installs only the basic functionality for the selected product.
■
Recommended filesets: installs the full feature set without optional filesets.
■
All filesets: installs all available filesets.
Each option displays the disk space that is required for installation. Select
which option you want to install and press Return.
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
10 After the system checks complete, the installer displays a list of the filesets to
be installed. Press Enter to continue with the installation.
11 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.
38
Installing Storage Foundation using the script-based installer
Installing Storage Foundation using the installer
39
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 Veritas products.
Keyless licensing requires that you manage the systems with a Management
Server.
See “About Veritas product licensing” on page 26.
14 The installer prompts you to configure SFHA. You can continue with
configuration if you answer y.
15 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
16 At the prompt, specify whether you want to send your installation information
to Symantec.
Would you like to send the information about this installation to
Symantec to help improve installation in the future? [y,n,q,?] (y) y
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 Veritas Web-based installer
■
Starting the Veritas Web-based installer
■
Obtaining a security exception on Mozilla Firefox
■
Performing a pre-installation check with the Veritas Web-based installer
■
Installing SF with the Web-based installer
About the Web-based installer
Use the Web-based installer interface to install Veritas 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 is operating. While
the installation processes are operating, the log files are located in a session-based
Installing Storage Foundation using the web-based installer
Before using the Veritas Web-based installer
directory under the /var/tmp directory. After the install process completes, the log
files are located in the /opt/VRTS/install/logs directory. It is recommended 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 Veritas Web-based installer” on page 41.
See “Starting the Veritas Web-based installer” on page 41.
Before using the Veritas Web-based installer
The Veritas Web-based installer requires the following configuration.
Table 7-1
Web-based installer requirements
System
Function
Requirements
Target system
The systems where you plan to install Must be a supported
the Veritas products.
platform for Veritas
Storage Foundation
6.0.1.
Installation server
The server where you start the
Must use the same
installation. The installation media is operating system as the
accessible from the installation server. target systems and must
be at one of the
supported operating
system update levels.
Administrative system
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 Veritas Web-based installer
This section describes starting the Veritas Web-based installer.
41
Installing Storage Foundation using the web-based installer
Obtaining a security exception on Mozilla Firefox
To start the Web-based installer
1
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, run the command again.
The default listening port is 14172. If you have a firewall that blocks port 14172,
use the -port option to use a free port instead.
2
On the administrative server, start the Web browser.
3
Navigate to the URL that the script displayed.
4
Certain browsers may display the following message:
Secure Connection Failed
Obtain a security exception for your browser.
When prompted, enter root and root's password of the installation server.
5
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).
5
Click Confirm Security Exception button.
6
Enter root in User Name field and root password of the web server in the
Password field.
42
Installing Storage Foundation using the web-based installer
Performing a pre-installation check with the Veritas Web-based installer
Performing a pre-installation check with the Veritas
Web-based installer
This section describes performing a pre-installation check with the Veritas
Web-based installer.
To perform a pre-installation check
1
Start the Web-based installer.
See “Starting the Veritas Web-based installer” on page 41.
2
On the Select a task and a product page, select Perform a Pre-installation
Check from the Task drop-down list. Select Veritas Storage Foundation and
High Availability from the Product drop-down list and click Next.
3
Select the 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 Veritas Web-based installer.
To install SF using the Web-based installer
1
Perform preliminary steps.
See “Performing a pre-installation check with the Veritas Web-based installer”
on page 43.
2
Start the Web-based installer.
See “Starting the Veritas Web-based installer” on page 41.
3
Select Install a Product from the Task drop-down list.
4
Select Storage Foundation from the Product drop-down list, and click Next.
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 filesets. Click Next.
43
Installing Storage Foundation using the web-based installer
Installing SF with the Web-based installer
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 tabs:
■
Keyless licensing
Note: The keyless license option enables you to install without entering a
key. However, in order 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
Complete the following information:
■
Choose whether you want to install Standard or Enterprise mode.
■
Choose whether you want to enable Veritas Replicator.
Click Register.
■
Enter license key
If you have a valid license key, select this tab. Enter the license key for
each system. Click Register.
11 For Storage Foundation, click Next to complete the configuration and start 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 can 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.
44
Installing Storage Foundation using the web-based installer
Installing SF with the Web-based installer
12 To configure Veritas 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 the installer displays the save location for the task log files, summary file,
and response file.
Click Finish button. If a message displays requesting a reboot, execute the
command to reboot the system.
/usr/sbin/shutdown -r now
13 If prompted, select the checkbox to specify whether you want to send your
installation information to Symantec.
Would you like to send the information about this installation
to Symantec to help improve installation in the future?
Click Finish. The installer asks if you would like to read the summary file. Select
Yes to read the summary file. If you select No, the installer prompts you for
another task.
45
Chapter
8
Performing an 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.
To install SF using response files
1
Make sure the systems where you want to install SF meet the installation
requirements.
2
Make sure 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.
Performing an automated installation using response files
Response file variables to install Storage Foundation
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.
See “About the Veritas installer” on page 22.
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
Description
CFG{opt}{install}
Installs SF filesets. Configuration can be performed at a
later time using the -configure option.
List or scalar: scalar
Optional or required: optional
CFG{opt}{installallpkgs}
or
CFG{opt}{installrecpkgs}
or
CFG{opt}{installminpkgs}
Instructs the installer to install SF filesets based on the
variable that has the value set to 1:
■
installallpkgs: Installs all filesets
■
installrecpkgs: Installs recommended filesets
■
installminpkgs: Installs minimum filesets
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
CFG{accepteula}
Specifies whether you agree with the EULA.pdf file on
the media.
List or scalar: scalar
Optional or required: required
47
Performing an automated installation using response files
Response file variables to install Storage Foundation
Table 8-1
Response file variables for installing SF (continued)
Variable
Description
CFG{opt}{vxkeyless}
Installs the product with keyless license.
List or scalar: scalar
Optional or required: optional
CFG{opt}{license}
Installs the product with permanent license.
List or scalar: scalar
Optional or required: optional
CFG{keys}{hostname}
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
CFG{systems}
List of systems on which the product is to be installed or
uninstalled.
List or scalar: list
Optional or required: required
CFG{prod}
Defines the product to be installed or uninstalled.
List or scalar: scalar
Optional or required: required
CFG{opt}{keyfile}
Defines the location of an ssh keyfile that is used to
communicate with all remote systems.
List or scalar: scalar
Optional or required: optional
CFG{opt}{pkgpath}
Defines a location, typically an NFS mount, from which
all remote systems can install product filesets. The
location must be accessible from all target systems.
List or scalar: scalar
Optional or required: optional
48
Performing an automated installation using response files
Sample response file for SF installation
Table 8-1
Response file variables for installing SF (continued)
Variable
Description
CFG{opt}{tmppath}
Defines the location where a working directory is created
to store temporary files and the filesets that are needed
during the install. The default location is /var/tmp.
List or scalar: scalar
Optional or required: optional
CFG{opt}{rsh}
Defines that rsh must be used instead of ssh as the
communication method between systems.
List or scalar: scalar
Optional or required: optional
CFG{opt}{logpath}
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
CFG{opt}{prodmode}
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{opt}{configure}=1;
$CFG{opt}{redirect}=1;
$CFG{opt}{vr}=1;
$CFG{prod}="SF60";
$CFG{systems}=[ qw(thoropt89 thoropt90) ];
1;
49
Performing an automated installation using response files
Configuring SF using response files
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.
To configure SF using response files
1
Make sure the SF filesets 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 50.
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 Veritas installer” on page 22.
Response file variables to configure Storage
Foundation
Table 8-2 lists the response file variables that you can define to configure SF.
Table 8-2
Response file variables specific to configuring Storage Foundation
Variable
List or Scalar
Description
$CFG{config_cfs}
Scalar
Performs the Cluster File System
configuration for SF.
(Required)
Set the value to 1 to configure
Cluster File System for SF.
50
Performing an automated installation using response files
Response file variables to configure Storage Foundation
Table 8-2
Response file variables specific to configuring Storage Foundation
(continued)
Variable
List or Scalar
Description
CFG{opt}{configure}
Scalar
Performs the configuration if the
filesets are already installed.
(Required)
Set the value to 1 to configure SF.
CFG{accepteula}
Scalar
Specifies whether you agree with
EULA.pdf on the media.
(Required)
CFG{systems}
List
List of systems on which the product
is to be configured.
(Required)
CFG{prod}
Scalar
Defines the product to be
configured.
The value is VCS60 for VCS.
(Required)
CFG{opt}{keyfile}
Scalar
Defines the location of an ssh keyfile
that is used to communicate with all
remote systems.
(Optional)
CFG{opt}{rsh}
Scalar
Defines that rsh must be used
instead of ssh as the communication
method between systems.
(Optional)
CFG{opt}{logpath}
Scalar
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)
51
Performing an automated installation using response files
Response file variables to configure Storage Foundation
Table 8-2
Response file variables specific to configuring Storage Foundation
(continued)
Variable
List or Scalar
Description
CFG{uploadlogs}
Scalar
Defines a Boolean value 0 or 1.
The value 1 indicates that the
installation logs are uploaded to the
Symantec Web site.
The value 0 indicates that the
installation logs are not uploaded to
the Symantec Web site.
(Optional)
Note that some optional variables make it necessary to define other optional
variables. For example, all the variables that are related to the cluster service group
(csgnic, csgvip, and csgnetmask) must be defined if any are defined. The same is
true for the SMTP notification (smtpserver, smtprecp, and smtprsev), the SNMP
trap notification (snmpport, snmpcons, and snmpcsev), and the Global Cluster
Option (gconic, gcovip, and gconetmask).
52
Chapter
9
Installing Storage
Foundation using operating
system-specific methods
This chapter includes the following topics:
■
Installing SF using NIM and the installer
■
Installing Storage Foundation using the mksysb utility
Installing SF using NIM and the installer
You can use the product installer in concert with Network Installation Manager (NIM)
to install the Veritas product, or to install the operating system with the Veritas
product.
The instructions in this section assume a working knowledge of the Network
Installation Management process. See the operating system documentation for
detailed information on Network Installation Management.
In the following samples, the LPP resource uses LPP-6100-up2date and its relevant
SPOT resource is spot-6100-up2date.
Preparing the installation bundle on the NIM server
You need to prepare the installation bundle on the NIM server before using NIM to
install SF filesets. The following actions are executed on the NIM server.
Note: Make sure that the appropriate NIM LPP_SOURCE and SPOT resources are
present on the NIM server.
Installing Storage Foundation using operating system-specific methods
Installing SF using NIM and the installer
To prepare the installation bundle
1
Insert and mount the installation media.
2
Choose an LPP source:
# lsnim |grep -i lpp_source
LPP-6100-up2date resources lpp_source
3
Navigate to the product directory on the installation media and run the
installsf command to prepare the bundle resource:
# ./installsf -nim LPP-6100-up2date
The installation program copies the necessary filesets and patches to the LPP
resource directory.
4
Enter a name for the bundle, for example SF601.
5
Run the lsnim -l command to check that the installp_bundle resource is
created successfully.
# lsnim -l SF601
SF601:
class = resources
type = installp_bundle
Rstate = ready for use
prev_state = unavailable for use
location = /opt/VRTS/nim/SF601.bnd
alloc_count = 0
server = master
Installing SF on the NIM client using SMIT on the NIM server
You can install SF on the NIM client using the SMIT tool on the NIM server.
Perform these steps on each node to have SF installed in a cluster.
To install SF
1
On the NIM server, start SMIT.
# smitty nim
2
In the menu, select Perform NIM Software Installation and Maintenance
Tasks.
3
In the menu, select Install and Update Software.
54
Installing Storage Foundation using operating system-specific methods
Installing SF using NIM and the installer
4
In the menu, select Install Software Bundle.
5
Select the systems from the list on which to install the software bundle.
6
In the menu, select the LPP_SOURCE. In this example, specify
LPP-6100-up2date.
7
If you are installing Storage Foundation, in the menu, select the bundle, for
example, SF601.
8
For the installp flags, specify that the ACCEPT new license agreements flag
has a yes value.
9
Press the Enter key to start the installation. Note that it may take some time
to finish.
10 After the installation completes, configure SF.
For instructions, see the chapter Configuring SF in this document.
Installing SF and the operating system on the NIM client using SMIT
You can install SF and the operating system on the NIM client using the SMIT tool.
Perform these steps on each node to have SF and AIX installed in a cluster.
To install SF and the operating system
1
On the NIM server, start smitty for a NIM and operating system installation.
# smitty nim_bosinst
2
In the menu, select the stand-alone target.
3
In the menu, select spot - Install a copy of a SPOT resource.
4
In the menu, select the spot resource spot-6100-up2date.
5
In the menu, select the LPP_SOURCE. In this example, select
LPP-6100-up2date.
6
In the menu, select the following options:
■
For the ACCEPT new license agreements option, specify yes.
■
For the Additional Bundles to Install option, specify SF601.
7
For the installp flags, specify that the ACCEPT new license agreements flag
has a yes value.
8
After the installation completes, configure SF.
For instructions, see the chapter Configuring SF in this document.
55
Installing Storage Foundation using operating system-specific methods
Installing Storage Foundation using the mksysb utility
Installing Storage Foundation using the mksysb utility
On AIX, one can use the mksysb utility to back up the system image. This image
can be installed on another host. For example, you can use this utility to set up a
disaster recovery site. Storage Foundation can be installed through mksysb image.
You can install the mksysb image on the same machine or on any NIM client through
a NIM server. This procedure assumes working knowledge of mksysb. See your
operating system installation guide for more details about mksysb.
The installation process involves the following steps:
■
Creating the mksysb image.
■
Installing the SF stack through mksysb image on a machine.
■
Verifying the installation.
Creating the mksysb backup image
You can create the mksysb backup image with the SMIT interface or with manual
steps.
Before you begin, make sure that the SF installation media is available.
To create an mksysb image using SMIT interface
1
Check maximum file size limit with ulimit. It should be sufficient for creating
backup image
2
Check that all the required filesets are installed for a particular product stack.
You can obtain the list of filesets from the the installer.
The recommended approach is to install all of the filesets but do not configure
product stack before taking mksysb image if the image is to be installed on a
different machine.
3
Enter fast path smitty mksysb and enter the required values.
4
Press enter to start the backup image creation.
56
Installing Storage Foundation using operating system-specific methods
Installing Storage Foundation using the mksysb utility
57
To create an mksysb image using commands manually
1
Check maximum file size limit with ulimit. It should be sufficient for creating
backup image
2
Check that all the required file sets are installed for a particular product stack.
You can obtain the list of filesets from the installer.
The recommended approach is to install all of the filesets but do not configure
product stack before taking mksysb image if the image is to be installed on a
different machine.
3
Enter command
# /usr/bin/mksysb
'-i' '-X'
backup_file_name
Installing mksysb image on alternate disk
You can install the mksysb image on the same system or on any NIM client through
a NIM server.
Before restoring mksysb on an alternate disk, perform the following steps to prepare
the target disk
1
Remove the disk from VM.
# vxdmpadm getsubpaths dmpnodename=disk_1 | grep hdisk
hdisk1
ENABLED(A)
-
sas0
Disk
# vxdisk rm disk_1
2
Clear the PV id of the target disk.
# chdev -l hdisk1 -a pv=clear
hdisk1 changed
To install SF with mksysb on an alternate disk of the same system using SMIT
1
Type smitty and then select Software Installation and Maintenance -> Alternate
Disk Installation -> Install mksysb on an Alternate Disk
2
Select target disks
3
Select mksysb image to be installed
4
Select appropriate values for remaining options
5
Press enter to start the mksysb image installation.
disk
Installing Storage Foundation using operating system-specific methods
Installing Storage Foundation using the mksysb utility
6
After installation is complete reboot from the alternate disk.
7
If SF was not configured in the mksysb image then run
58
/opt/VRTS/install/installsf<version> -configure after reboot.
Where <version> is the specific release version.
See “About the Veritas installer” on page 22.
To install SF with mksysb on an alternate disk of the same system using commands
manually
◆
To install SF with mksysb on an alternate disk of the same system using
commands manually
# /usr/sbin/alt_disk_mksysb -m mksysb_image -P "all" -d "disk_name"
To install SF with mksysb on an alternate disk of the NIM client using SMIT
1
Create an mksysb resource from the mksysb image created above on NIM
server.
2
Set up the system on which you want to install SF as NIM client.
3
Type smitty nim then select Perform NIM Software Installation and Maintenance
Tasks -> Alternate Disk Installation -> Install mksysb on an Alternate Disk
4
Select target system.
5
Select target disks.
6
Select mksysb image to be installed.
7
Select appropriate values for remaining options.
8
Press enter to start the mksysb image installation.
9
If SF was not configured in the mksysb image then run
/opt/VRTS/install/installsf<version> -configure after rebooting NIM
client.
Where <version> is the specific release version.
See “About the Veritas installer” on page 22.
To install SF with mksysb on an alternate disk of a NIM client using commands
manually
1
Create an mksysb resource from the mksysb image created above on NIM
server.
2
Set up the system on which you want to install SF as NIM client.
Installing Storage Foundation using operating system-specific methods
Installing Storage Foundation using the mksysb utility
3
To install SF with mksysb on an alternate disk of a NIM client using commands
manually:
# /usr/sbin/nim -o alt_disk_install \
-a source=mksysb
-a mksysb=mksysb_resource -a \
disk=hdisk_name system_name
4
If SF was not configured in the mksysb image then run
/opt/VRTS/install/installsf<version> -configure after rebooting NIM
client.
Where <version> is the specific release version.
See “About the Veritas installer” on page 22.
Verifying the installation
After the installation is finished, verify the installation using the following command:
# lslpp -l|grep -i vrts
All the filesets should be installed properly.
See “Discovering product versions and various requirement information” on page 18.
59
Chapter
10
Configuring Storage
Foundation
This chapter includes the following topics:
■
Configuring Storage Foundation using the installer
■
Configuring Storage Foundation manually
■
Configuring DMP support for booting over a SAN
■
Configuring the Storage Foundation for Databases repository database after
installation
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 installation directory.
2
Run the installer command with the configure option.
# ./installer -configure
Configuring Storage Foundation manually
You can manually configure different products within Storage Foundation.
Configuring Storage Foundation
Configuring DMP support for booting over a SAN
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/filesystems
The Veritas-specific commands are described in the Storage Foundation guides
and online manual pages.
See the Veritas Storage Foundation Administrator's Guide.
Configuring DMP support for booting over a SAN
For DMP to work with an LVM root disk over a SAN, configure the system to use
the boot device over all possible paths.
61
Configuring Storage Foundation
Configuring DMP support for booting over a SAN
To configure DMP support for booting over a SAN
1
Verify that each path to the root device has the same physical volume identifier
(PVID) and the same volume group. Use the lspv command for the root volume
group to verify that the PVID and volume group entries are set correctly. The
PVID and volume group entries in the second and third columns of the output
should be identical for all the paths.
In this example, the LVM root disk is multi-pathed with four paths. The output
from the lspv command for the root volume group (rootvg) is as follows:
# lspv | grep rootvg
hdisk374
hdisk375
hdisk376
hdisk377
2
00cbf5ce56def54d
00cbf5ce56def54d
00cbf5ce56def54d
00cbf5ce56def54d
rootvg active
rootvg
rootvg
rootvg
If the PVID and volume group entries are not set correctly on any of the paths,
use the chdev command to set the correct value.
For example, the following output shows that the hdisk377 path is not set
correctly:
# lspv
hdisk374
hdisk375
hdisk376
hdisk377
00cbf5ce56def54d
00cbf5ce56def54d
00cbf5ce56def54d
none
rootvg active
rootvg
rootvg
None
To set the PVID for the path, use the following command:
# chdev -l hdisk377 -a pv=yes
hdisk377 changed
The output of the lspv command now shows the correct values:
# lspv | grep rootvg
hdisk374
hdisk375
hdisk376
hdisk377
00cbf5ce56def54d
00cbf5ce56def54d
00cbf5ce56def54d
00cbf5ce56def54d
rootvg active
rootvg
rootvg
rootvg
62
Configuring Storage Foundation
Configuring DMP support for booting over a SAN
3
Set the boot list to include all the paths of current boot disk.
# bootlist -m normal hdisk374 hdisk375 hdisk376 hdisk377 blv=hd5
Verify that the boot list includes all paths and that each path shows the default
boot volume hd5:
# bootlist -m normal -o
hdisk374
hdisk375
hdisk376
hdisk377
4
blv=hd5
blv=hd5
blv=hd5
blv=hd5
If the blv option is not set for a path to the disk, use the bootlist command
to set it. For example:
# bootlist -m normal hdisk374 hdisk375 hdisk376 hdisk377 blv=hd5
5
Run one of the following commands to configure DMP on the root disk:
■
The recommended method is to turn on DMP support for LVM volumes,
including the root volume.
# vxdmpadm settune dmp_native_support=on
■
The following command enables DMP support for LVM volumes only for
the root disk. This method will be deprecated in a future release.
# vxdmpadm native enable vgname=rootvg
6
Reboot the system. DMP takes control of the SAN boot device to perform load
balancing and failover.
7
Verify whether DMP controls the root disk.
# vxdmpadm native list vgname=rootvg
PATH
DMPNODENAME
===========================
hdisk374
ams_wms0_491
hdisk375
ams_wms0_491
hdisk376
ams_wms0_491
hdisk377
ams_wms0_491
63
Configuring Storage Foundation
Configuring the Storage Foundation for Databases repository database after installation
Configuring the Storage Foundation for Databases
repository database after installation
If you want to use Storage Foundation for Databases (SFDB), you must set up the
SFDB repository after installing and configuring SF and . For SFDB repository set
up procedures:
See Veritas Storage Foundation: Storage and Availability Management for
Databases
64
Section
3
Upgrade of SF
■
Chapter 11. Planning to upgrade SF
■
Chapter 12. Upgrading Storage Foundation
■
Chapter 13. Performing an automated SF upgrade using response files
■
Chapter 14. Upgrading SF using an alternate disk
■
Chapter 15. Upgrading SF using Network Install Manager Alternate Disk
Migration
■
Chapter 16. Migrating from Storage Foundation Basic to Storage Foundation
Standard
■
Chapter 17. Performing post-upgrade tasks
Chapter
11
Planning to upgrade SF
This chapter includes the following topics:
■
Upgrade methods for SF
■
Supported upgrade paths for SF 6.0.1
■
Preparing to upgrade SF
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 11-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 Veritas provided
Script-based—you can use this to upgrade
tool or you can perform the upgrade manually. for the supported upgrade paths
Requires some server downtime.
Web-based—you can use this to upgrade for
the supported upgrade paths
Manual—you can use this to upgrade from
the previous release
Response file—you can use this to upgrade
from the supported upgrade paths
Native operating system upgrade—use the Operating system specific methods
upgrade software that comes with the
Operating system upgrades
operating system. Note that not all operating
systems support native upgrades.
Planning to upgrade SF
Supported upgrade paths for SF 6.0.1
Supported upgrade paths for SF 6.0.1
The following tables describe upgrading to 6.0.1.
Table 11-2
AIX upgrades using the script- or Web-based installer
Veritas
software
version
AIX 5.2
AIX 5.3
4.0
Upgrade the
operating system
to AIX 5.3 TL7
with SP2 or
later—do not
upgrade to AIX
6.1 or 7.1.
Upgrade your
Veritas product
to 5.0 MP3RP1.
Then upgrade
the operating
system to AIX
6.1 TL5 or
later—do not
upgrade to 7.1.
Use the installer
to upgrade your
Veritas product
to 6.0.1.
Upgrade the
N/A
operating system
to AIX 5.3 TL7
with SP2 or
later—do not
upgrade to AIX
6.1 or 7.1.
Upgrade your
Veritas product
to 5.0 MP3RP1.
Then upgrade
the operating
system to AIX
6.1 TL5 or
later—do not
upgrade to 7.1.
Use the installer
to upgrade your
Veritas product
to 6.0.1.
Then, upgrade
the operating
system to AIX
7.1 if you want to
use your Veritas
product on AIX
7.1.
Then, upgrade
the operating
system to AIX
7.1 if you want to
use your Veritas
product on AIX
7.1.
4.0 MPx
5.0
AIX 6.1
AIX 7.1
N/A
67
Planning to upgrade SF
Supported upgrade paths for SF 6.0.1
Table 11-2
AIX upgrades using the script- or Web-based installer (continued)
Veritas
software
version
AIX 5.2
AIX 5.3
AIX 6.1
AIX 7.1
5.0 MP1
Upgrade the
operating system
to AIX 5.3 TL7
with SP2 or
later—do not
upgrade to AIX
6.1 or 7.1.
Upgrade your
Veritas product
to 5.0 MP3RP1.
Then upgrade
the operating
system to AIX
6.1 TL5 or
later—do not
upgrade to 7.1.
Use the installer
to upgrade your
Veritas product
to 6.0.1.
Upgrade the
operating system
to AIX 5.3 TL7
with SP2 or
later—do not
upgrade to AIX
6.1 or 7.1.
Upgrade your
Veritas product
to 5.0 MP3RP1.
Then upgrade
the operating
system to AIX
6.1 TL5 or
later—do not
upgrade to 7.1.
Use the installer
to upgrade your
Veritas product
to 6.0.1.
Upgrade the
N/A
operating system
to AIX 6.1 TL0
with SP4 or
later—do not
upgrade to AIX
6.1 TL2 or 7.1.
Upgrade your
Veritas product
to 5.0 MP3RP1.
Upgrade the
operating system
to AIX 6.1 TL5 or
later—do not
upgrade to AIX
7.1. Then use
the installer to
upgrade to your
Veritas product
to 6.0.1.
Then, upgrade
the operating
system to AIX
7.1 if you want to
use your Veritas
product on AIX
7.1.
Then, upgrade
the operating
system to AIX
7.1 if you want to
use your Veritas
product on AIX
7.1.
Then, upgrade
the operating
system to AIX
7.1 if you want to
use your Veritas
product on AIX
7.1.
68
Planning to upgrade SF
Supported upgrade paths for SF 6.0.1
Table 11-2
AIX upgrades using the script- or Web-based installer (continued)
Veritas
software
version
AIX 5.2
AIX 5.3
AIX 6.1
AIX 7.1
5.0 MP3
N/A
If your Veritas
product version
is 5.0MP3,
upgrade your
Veritas product
to 5.0MP3RP1.
If your Veritas
product version
is 5.0MP3,
upgrade your
Veritas product
to 5.0MP3RP1.
N/A
Upgrade the
operating system
to AIX 6.1 TL5 or
later—do not
upgrade to AIX
7.1. Then use
the installer to
upgrade your
Veritas product
to 6.0.1.
Upgrade the
operating system
to AIX 6.1 TL5 or
later—do not
upgrade to AIX
7.1. Then use
the installer to
upgrade your
Veritas product
to 6.0.1.
Then, upgrade
the operating
system to AIX
7.1 if you want to
use your Veritas
product on AIX
7.1.
Then, upgrade
the operating
system to AIX
7.1 if you want to
use your Veritas
product on AIX
7.1.
5.0 MP3 RPx
69
Planning to upgrade SF
Supported upgrade paths for SF 6.0.1
Table 11-2
AIX upgrades using the script- or Web-based installer (continued)
Veritas
software
version
AIX 5.2
AIX 5.3
AIX 6.1
5.1
N/A
Upgrade the
operating system
to AIX 6.1 TL5 or
later—do not
upgrade to AIX
7.1. Then use
the installer to
upgrade your
Veritas product
to 6.0.1.
Upgrade the
N/A
operating system
to AIX 6.1 TL5 or
later—do not
upgrade to AIX
7.1. Then use
the installer to
upgrade your
Veritas product
to 6.0.1.
Then, upgrade
the operating
system to AIX
7.1 if you want to
use your Veritas
product on AIX
7.1.
Then, upgrade
the operating
system to AIX
7.1 if you want to
use your Veritas
product on AIX
7.1.
5.1 RPx
5.1 SP1
5.1 SP1 RPx
AIX 7.1
5.1 SP1 PR1
N/A
N/A
N/A
Use the installer
to upgrade your
Veritas product
to 6.0.1.
No Veritas
product
N/A
N/A
Upgrade the
operating system
to AIX 6.1 TL5 or
later. Use the
installer to install
the 6.0.1 version
of your Veritas
product.
Use the installer
to install the
6.0.1 version of
your Veritas
product.
6.0
N/A
N/A
Use the installer
to upgrade your
Veritas product
to 6.0.1.
Use the installer
to upgrade your
Veritas product
to 6.0.1.
6.0 RP1
70
Planning to upgrade SF
Preparing to upgrade SF
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 Veritas 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 72.
■
Ensure that you have enough file system space to upgrade. Identify where you
want to copy the filesets, 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 on a file system that is inaccessible prior to running the
upgrade script.
You can use a Veritas-supplied disc for the upgrade as long as modifications
to the upgrade script are not required.
■
For any startup scripts in /sbin/rcS.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.0.1 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 Veritas products. Depending on the configuration, the
outage can take several hours.
■
Make sure the file systems are clean before upgrading.
See “Verifying that the file systems are clean” on page 76.
■
Upgrade arrays (if required).
See “Upgrading the array support” on page 77.
71
Planning to upgrade SF
Preparing to upgrade SF
■
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.
Preparing for an upgrade of Storage Foundation
Before the upgrade of Storage Foundation to a new release, synchronize snapshots.
To prepare for an upgrade of Storage Foundation
1
Log in as root.
2
Stop activity to all file systems and raw volumes, for example by unmounting
any file systems that have been created on volumes.
# umount mnt_point
3
Stop all the volumes by entering the following command for each disk group:
# vxvol -g diskgroup stopall
4
Stop the VEA backend service by entering the following command if VRTSob
is installed:
# /opt/VRTS/bin/vxsvcctrl stop
5
Upgrade AIX on your system to the required levels if applicable.
Creating backups
Save relevant system information before the upgrade.
To create backups
1
Log in as superuser.
2
Make a record of the mount points for VxFS file systems and VxVM volumes
that are defined in the /etc/filesystems file. You need to recreate these
entries in the /etc/filesystems file on the freshly upgraded system.
3
Before the upgrade, ensure that you have made backups of all data that you
want to preserve.
72
Planning to upgrade SF
Preparing to upgrade SF
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 filesystems file to filesystems.orig:
# cp /etc/filesystems /etc/filesystems.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 are installing the high availability version of the Veritas Storage
Foundation 6.0.1 software, follow the guidelines given in the Veritas Cluster
Server Installation Guide and Veritas Cluster Server Release Notes for
information on preserving your VCS configuration across the installation
procedure.
Tasks for upgrading the Storage Foundation for Databases (SFDB)
Tasks for upgrading SFDB tools to version 6.0.1:
■
Preparing to migrate the repository database before upgrading from 5.0x or
earlier to 6.0.1
See “Pre-upgrade tasks for migrating the SFDB repository database” on page 73.
■
Migrating the repository database after upgrading from 5.0.x or earlier to 6.0.1
See “Post upgrade tasks for migrating the SFDB repository database”
on page 109.
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.0.1 before upgrading
to Storage Foundation or Storage Foundation for Oracle RAC 6.0.1.
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.0.1.
Perform the following before upgrading SF.
73
Planning to upgrade SF
Preparing to upgrade 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.0.1.
Pre-upgrade planning for Veritas Volume Replicator
Before installing or upgrading Veritas 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
■
If replication using VVR is configured, make sure the size of the SRL volume is
greater than 110 MB.
Refer to the Veritas 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 Veritas Storage Foundation and High Availability Solutions Replication
Administrator's Guide for more information.
See the Getting Started Guide for more information on the documentation.
74
Planning to upgrade SF
Preparing to upgrade SF
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 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 11-3, if either the Primary or Secondary are running a version of VVR prior
to 6.0.1, and you use the TCP protocol, VVR calculates the checksum for every
data packet it replicates. If the Primary and Secondary are at VVR 6.0.1, VVR does
not calculate the checksum. Instead, it relies on the TCP checksum mechanism.
Table 11-3
VVR versions and checksum calculations
VVR prior to 6.0.1
VVR 6.0.1
(DG version <= 140)
(DG version >= 150)
Primary
Secondary
Yes
Secondary
Primary
Yes
Primary and Secondary
VVR calculates checksum
TCP connections?
Yes
Primary and Secondary
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.
75
Planning to upgrade SF
Preparing to upgrade SF
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
■
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
Verifying that the file systems are clean
Verify that all file systems have been cleanly unmounted.
76
Planning to upgrade SF
Preparing to upgrade SF
To make sure the file systems are clean
1
Verify that all file systems have been cleanly unmounted:
# echo "8192B.p S" | /opt/VRTSvxfs/sbin/fsdb filesystem | \
grep clean
flags 0 mod 0 clean clean_value
A clean_value value of 0x5a indicates the file system is clean. A value of 0x3c
indicates the file system is dirty. A value of 0x69 indicates the file system is
dusty. A dusty file system has pending extended operations.
2
If a file system is not clean, enter the following commands for that file system:
# opt/VRTS/bin/fsck -V vxfs filesystem
# opt/VRTS/bin/mount -V vxfs filesystem mountpoint
# opt/VRTS/bin/umount mountpoint
These commands should complete any extended operations on the file system
and unmount the file system cleanly.
A pending large fileset clone removal extended operation might be in progress
if the umount command fails with the following error:
file system device busy
An extended operation is in progress if the following message is generated on
the console:
Storage Checkpoint asynchronous operation on file_system
file system still in progress.
3
If an extended operation is in progress, you must leave the file system mounted
for a longer time to allow the operation to complete. Removing a very large
fileset clone can take several hours.
4
Repeat step 1 to verify that the unclean file system is now clean.
Upgrading the array support
The Storage Foundation 6.0.1 release includes all array support in a single fileset,
VRTSaslapm. The array support fileset includes the array support previously included
in the VRTSvxvm fileset. The array support fileset also includes support previously
packaged as external array support libraries (ASLs) and array policy modules
(APMs).
See the 6.0.1 Hardware Compatibility List for information about supported arrays.
77
Planning to upgrade SF
Preparing to upgrade SF
See “Hardware compatibility list (HCL)” on page 17.
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 fileset
exits with an error if external ASLs or APMs are detected.
After you have installed Storage Foundation 6.0.1, Symantec provides support for
new disk arrays through updates to the VRTSaslapm fileset.
For more information about array support, see the Veritas Storage Foundation
Administrator's Guide.
78
Chapter
12
Upgrading Storage
Foundation
This chapter includes the following topics:
■
Upgrading Storage Foundation with the product installer
■
Upgrading Storage Foundation using the Veritas Web-based installer
■
Upgrade Storage Foundation and AIX on a DMP-enabled rootvg
■
Upgrading using SMIT
■
Upgrading the AIX operating system
■
Upgrading Veritas Volume Replicator
Upgrading Storage Foundation with the product
installer
This section describes upgrading from Storage Foundation products to 6.0.1.
To upgrade Storage Foundation
1
Log in as superuser.
2
Unmount any mounted VxFS file systems.
The installer supports the upgrade of multiple hosts, if each host is running the
same version of VxVM and VxFS. Hosts must be upgraded separately if they
are running different versions.
If any VxFS file systems are mounted with the QuickLog feature, QuickLog
must be disabled before upgrading. See the "Veritas QuickLog" chapter of the
Storage Foundation Administrator’s Guide for more information.
Upgrading Storage Foundation
Upgrading Storage Foundation with the product installer
3
If replication using VVR is configured, verify that all the Primary RLINKs are
up-to-date:
# /usr/sbin/vxrlink -g diskgroup status rlink_name
Note: Do not continue until the Primary RLINKs are up-to-date.
4
Load and mount the disc. If you downloaded the software, navigate to the top
level of the download directory.
5
From the disc, run the installer command. If you downloaded the software,
run the ./installer command.
# cd /cdrom/cdrom0
# ./installer
6
Enter G to upgrade and select the Full Upgrade.
7
You are prompted to enter the system names (in the following example, "sys1")
on which the software is to be installed. Enter the system name or names and
then press Return.
Enter the system names separated by spaces on which to
install SF: sys1 sys2
Depending on your existing configuration, various messages and prompts may
appear. Answer the prompts appropriately.
8
The installer asks if you agree with the terms of the End User License
Agreement. Press y to agree and continue.
9
The installer lists the filesets to install or to update. You are prompted to confirm
that you are ready to upgrade.
10 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.
11 The installer stops, uninstalls, reinstalls, and starts specified filesets.
80
Upgrading Storage Foundation
Upgrading Storage Foundation using the Veritas Web-based installer
81
12 If the upgrade was done from 5.0 or if the Storage Foundation was done without
vxkeyless keys, the installer shows the following warning:
CPI WARNING V-9-40-5323 SF license version 5.0 is not
updated to 6.0 on sys1. It's recommended to upgrade to a 6.0 key.
CPI WARNING V-9-40-5323 SF license version 5.0 is not updated
to 6.0 on sys2. It's recommended to upgrade to a 6.0 key.
SF is licensed on the systems.
Do you wish to enter additional licenses? [y,n,q,b] (n) n
13 The Storage Foundation software is verified and configured.
14 The installer prompts you to provide feedback, and provides the log location
for the upgrade.
Upgrading Storage Foundation using the Veritas
Web-based installer
This section describes upgrading SF with the Veritas 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 wish to preserve. For
example, make configuration file backups.
2
Start the Web-based installer.
See “Starting the Veritas Web-based installer” on page 41.
3
On the Select a task and a product page, select Upgrade a Product from the
Task drop-down menu.
The installer detects the product that is installed on the specified system. Click
Next.
4
Indicate the systems on which to upgrade. Enter one or more system names,
separated by spaces. Click Next.
5
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.
6
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.
Upgrading Storage Foundation
Upgrade Storage Foundation and AIX on a DMP-enabled rootvg
7
If you are prompted to reboot the systems, enter the following reboot command:
# /usr/sbin/shutdown -r now
8
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 will not ask any questions.
9
Click Finish. The installer prompts you for another task.
Upgrade Storage Foundation and AIX on a
DMP-enabled rootvg
The following upgrade paths are supported to upgrade SF and AIX on a
DMP-enabled rootvg
Table 12-1
Upgrade paths for SF on a DMP-enabled rootvg
Upgrade path
Procedure
Prior version of SF on AIX 6.1
See “Upgrading from prior version of SF on AIX 6.1 to
SF 6.0.1 on a DMP-enabled rootvg” on page 82.
Prior version of SF on AIX 5.3
See “Upgrading from a prior version of SF on AIX 5.3
to SF 6.0.1 on AIX 6.1 or AIX 7.1 on a DMP-enabled
rootvg” on page 83.
SF 6.0 on AIX 6.1 to SF 6.0.1 on
AIX 7.1
See “Upgrading from SF 6.0.1 on AIX 6.1 to SF 6.0.1
on AIX 7.1 on a DMP-enabled rootvg ” on page 84.
Upgrading from prior version of SF on AIX 6.1 to SF 6.0.1 on a
DMP-enabled rootvg
When you upgrade from a prior version of SF on a DMP-enabled rootvg to SF 6.0.1,
you must disable DMP root support before performing the upgrade. Enable the
DMP root support after the upgrade. If the AIX version is less than 6.1, an operating
system upgrade is required.
See “Upgrading from a prior version of SF on AIX 5.3 to SF 6.0.1 on AIX 6.1 or AIX
7.1 on a DMP-enabled rootvg” on page 83.
82
Upgrading Storage Foundation
Upgrade Storage Foundation and AIX on a DMP-enabled rootvg
83
To upgrade from SF to SF 6.0.1 on a DMP-enabled rootvg
1
Disable DMP support for the rootvg:
For release SF 5.1 or later:
# vxdmpadm native disable vgname=rootvg
Please reboot the system to disable DMP support for LVM
bootability
For release prior to SF 5.1:
# vxdmproot uninstall
Please reboot the system to disable DMP support for LVM bootability
2
Reboot the system.
3
Upgrade SF to 6.0.1.
Run the installer command on the disc, and enter G for the upgrade task.
See “Upgrading Storage Foundation with the product installer” on page 79.
4
Reboot the system.
5
Enable DMP for rootvg.
# vxdmpadm native enable vgname=rootvg
Please reboot the system to enable DMP support for LVM bootability
6
Reboot the system. After the reboot, the system has DMP root support enabled.
Upgrading from a prior version of SF on AIX 5.3 to SF 6.0.1 on AIX
6.1 or AIX 7.1 on a DMP-enabled rootvg
SF 6.0.1 requires at least AIX 6.1. When you upgrade SF from a prior version on
a system that uses AIX 5.3, you must also upgrade the AIX operating system. If
the rootvg is enabled for DMP, follow these steps.
Upgrading Storage Foundation
Upgrade Storage Foundation and AIX on a DMP-enabled rootvg
To upgrade from a prior version of SF to SF 6.0.1 on a DMP-enabled rootvg
1
Disable DMP support for the rootvg:
For release SF 5.1 or later:
# vxdmpadm native disable vgname=rootvg
Please reboot the system to disable DMP support for LVM
bootability
For release prior to SF 5.1:
# vxdmproot uninstall
Please reboot the system to disable DMP support for LVM
bootability
2
Upgrade the AIX operating system from 5.3 to 6.1 before rebooting.
3
Reboot the system.
4
Upgrade SF to 6.0.1.
See “Upgrading Storage Foundation with the product installer” on page 79.
Restart the system if the installer prompts for restart during upgrade.
If vxconfigd cannot be started after the upgrade, restart the system.
5
Enable DMP for rootvg.
# vxdmpadm native enable vgname=rootvg
Please reboot the system to enable DMP support for LVM
bootability
6
Reboot the system. After the reboot, the system has DMP root support enabled.
Upgrading from SF 6.0.1 on AIX 6.1 to SF 6.0.1 on AIX 7.1 on a
DMP-enabled rootvg
When you upgrade the operating system from AIX 6.1 to AIX 7.1 while SF is at
6.0.1 level on a DMP-enabled rootvg, DMP root support is automatically enabled.
To upgrade AIX with DMP-enabled rootvg
1
Upgrade the AIX operating system from 6.1 to 7.1.
2
Reboot the system. After the reboot, the system has DMP root support enabled.
84
Upgrading Storage Foundation
Upgrading using SMIT
Upgrading using SMIT
To uncompress the filesets:
1
Log in as superuser.
2
Create an installation directory on your system large enough for all the Storage
Foundation patches. Refer to the disk space requirements in the system
requirements section.
# mkdir /tmp/install
3
Place the Veritas software disc into a DVD drive connected to your system. If
you downloaded the software, navigate to the top level of the download directory
and perform the steps without the DVD.
4
Mount the disk by determining the device access name of the DVD drive. The
format for the device access name is cdN where N is the device number. After
inserting the disk into the DVD drive, enter:
# mkdir -p /mnt/cdrom
# mount -V cdrfs -o ro /dev/cdrom /mnt/cdrom
5
Copy the compressed patch files and the table of contents (.toc) file from the
software disc to the temporary directory.
# cp -r * /tmp/install
# cp .toc /tmp/install/
The .toc specifies the order in which the Storage Foundation components
must be installed, and is used by the installp command. In general VRTSveki,
VRTSvxvm, and VRTSvxfs must be installed first in the specified order.
6
Change to the temporary directory:
# cd /tmp/install
7
Invoke SMIT from the command line to upgrade the system. First, upgrade the
already installed components of Storage Foundation (formerly known as
Foundation Suite):
# cd /tmp/install
# smitty update_all
85
Upgrading Storage Foundation
Upgrading the AIX operating system
8
Once the existing components have been upgraded, add the new components
added to the 6.0.1 release with this command:
# smitty install
9
After successful upgrade, you must reboot the system. Reboot using the
command:
# shutdown -r
10 To take advantage of new features, upgrade the VxVM disk group version (90)
to the latest (140).
See the vxdg manual pages for more details.
Upgrading the AIX operating system
Use this procedure to upgrade the AIX operating system if SF 6.0.1 is installed.
You must upgrade to a version that SF 6.0.1 supports.
To upgrade the AIX operating system
1
Create the install-db file.
# touch /etc/vx/reconfig.d/state.d/install-db
2
Stop activity to all file systems and raw volumes, for example by unmounting
any file systems that have been created on volumes.
# umount mnt_point
3
Stop all the volumes by entering the following command for each disk group:
# vxvol -g diskgroup stopall
4
Stop the VEA backend service by entering the following command:
# /opt/VRTS/bin/vxsvcctrl stop
5
Upgrade the AIX operating system. See the operating system documentation
for more information.
6
Apply the necessary APARs.
For information about APARs required for Storage Foundation 6.0.1, refer to
the Storage Foundation Release Notes.
86
Upgrading Storage Foundation
Upgrading Veritas Volume Replicator
7
Enable SF to start after you reboot.
# rm /etc/vx/reconfig.d/state.d/install-db
8
Reboot the system.
# shutdown -Fr
Upgrading Veritas Volume Replicator
If a previous version of Veritas Volume Replicator (VVR) is configured, the product
installer upgrades VVR automatically when you upgrade the Storage Foundation
products.
When upgrading from 4.0 or later, you have the option to upgrade without disrupting
replication.
See “Upgrading VVR without disrupting replication” on page 87.
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 75.
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.
87
Upgrading Storage Foundation
Upgrading Veritas Volume Replicator
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
2
Upgrade from VVR 5.1 or later to VVR 6.0.1 on the Secondary.
3
Do one of the following:
■
Upgrade the disk group now. Enter the following:
# vxdg upgrade dgname
■
4
Upgrade the disk group later.
If you upgrade the disk group later, be sure to pause replication before you
upgrade the disk group.
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 Veritas 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.0.1 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.
88
Upgrading Storage Foundation
Upgrading Veritas Volume Replicator
If you upgrade the disk group later, be sure to pause replication before you
upgrade the disk group.
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 75.
89
Chapter
13
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.
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 one of the systems 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
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 13-1 lists the response file variables that you can define to configure SF.
Table 13-1
Response file variables for upgrading SF
Variable
Description
CFG{accepteula}
Specifies whether you agree with the EULA.pdf file on
the media.
List or scalar: scalar
Optional or required: required
CFG{systems}
List of systems on which the product is to be installed or
uninstalled.
List or scalar: list
Optional or required: required
CFG{opt}{keyfile}
Defines the location of an ssh keyfile that is used to
communicate with all remote systems.
List or scalar: scalar
Optional or required: optional
CFG{opt}{tmppath}
Defines the location where a working directory is created
to store temporary files and the filesets that are needed
during the install. The default location is /var/tmp.
List or scalar: scalar
Optional or required: optional
91
Performing an automated SF upgrade using response files
Sample response file for SF upgrade
Table 13-1
Response file variables for upgrading SF (continued)
Variable
Description
CFG{opt}{logpath}
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
CFG{opt}{upgrade}
Upgrades all filesets installed, without configuration.
List or scalar: list
Optional or required: optional
CFG{mirrordgname}{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
CFG{splitmirror}{system}
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
Sample response file for SF upgrade
The following example shows a response file for upgrading Storage Foundation.
our %CFG;
$CFG{accepteula}=1;
$CFG{opt}{upgrade}=1;
$CFG{systems}=[ qw(system01) ];
1;
92
Chapter
14
Upgrading SF using an
alternate disk
This chapter includes the following topics:
■
About upgrading SF using an alternate disk
■
Supported upgrade scenarios
■
Supported upgrade paths for SF using alternate disks
■
Preparing to upgrade SF on an alternate disk
■
Upgrading SF on an alternate disk
■
Verifying the upgrade
About upgrading SF using an alternate disk
Use the alternate disk installation process to upgrade the operating system and SF
on a production server while the server runs. Perform the upgrade on an alternate
or inactive boot environment. After the upgrade, restart the system on the alternate
disk to use the updated environment. The instructions in this section assume a
working knowledge of the alternate disk installation process. See the operating
system documentation for detailed information on alternate disk installations.
Note: Only Technology Level (TL) and Service Pack (SP) releases of the operating
system can be upgraded using this procedure.
Upgrading SF on an alternate disk has the following advantages:
■
The server remains active during the time the new boot environment is created
and upgraded on the alternate boot device.
Upgrading SF using an alternate disk
Supported upgrade scenarios
■
The actual downtime for the upgrade is reduced to the period of time required
for a single reboot.
■
The original boot environment is still available for use if the updated environment
fails to become active.
Supported upgrade scenarios
The following upgrade scenarios are supported on an alternate disk:
■
Upgrading only SF
See “ Upgrading SF on an alternate disk” on page 96.
■
Upgrading only the operating system (Technology Level (TL) and Service Pack
(SP) releases)
Note: For instructions, see the operating system documentation. No additional
steps are required for SF after the operating system upgrade.
■
Upgrading the operating system (Technology Level (TL) and Service Pack (SP)
releases) and SF
See “ Upgrading SF on an alternate disk” on page 96.
Supported upgrade paths for SF using alternate disks
You can upgrade the operating system and SF using an alternate disk from the
following versions:
AIX version
Technology Level and Service Pack releases of AIX 6.1 and AIX
7.1
SF version
See “Supported upgrade paths for SF 6.0.1” on page 67.
Preparing to upgrade SF on an alternate disk
Complete the preparatory steps in the following procedure before you upgrade SF
on an alternate disk.
94
Upgrading SF using an alternate disk
Preparing to upgrade SF on an alternate disk
To prepare to upgrade SF on an alternate disk
1
Make sure that the SF installation media is available.
2
Check the status of the physical disks on your system.
Note: The alternate disk must have a physical identifier and must not contain
any mounted volume groups.
# lspv
Output similar to the following displays:
hdisk0
0009710fa9c79877
rootvg
hdisk1
0009710f0b90db93
None
active
If the alternate disk does not have a physical identifier, set the physical identifier
for the disk:
# chdev -l hdisk1 -a pv=yes
3
Make sure that the following filesets are installed on the primary disk:
bos.alt_disk_install.boot_images, bos.alt_disk_install.rte
# lslpp -l -a | grep bos.alt_disk_install
4
Mount the SF installation media.
Determine the filesets you want to install on the alternate disk.
# ./installsf -install_option
where install_option is one of the following:
-minpkgs: For installing the minimum set of filesets
-recpkgs: For installing the recommended filesets
-allpkgs: For installing all filesets
Copy the required filesets from the pkgs directory on the installation media to
a directory on the primary boot disk, for example /tmp/prod_name
If you are upgrading the operating system along with SF, copy the necessary
operating system filesets and the SF filesets to a directory on the primary disk,
for example /tmp/prod_name.
See the operating system documentation to determine the operating system
filesets.
95
Upgrading SF using an alternate disk
Upgrading SF on an alternate disk
96
Upgrading SF on an alternate disk
This section provides instructions to clone the primary boot environment to the
alternate disk, upgrade SF on the alternate disk, and reboot the system to start
from the alternate disk. You may perform the steps manually or using the SMIT
interface.
In the procedure examples, the primary or current boot environment resides on
hdisk0 and the alternate or inactive boot environment resides on hdisk1.
To upgrade SF on an alternate disk
1
Clone the primary boot disk rootvg to an alternate disk using one of the
following methods:
Manual
Run the following command:
# /usr/sbin/alt_disk_copy -I "acNgXY" -P "all" \
-l "/tmp/prod_name" -w "all" -d "hdisk1"
Where:
■
■
■
-d indicates the name of the target disk on which you clone
the primary disk.
-l indicates the full path of the directory that contains the
filesets to be upgraded
-w indicates the list of SF filesets that you want to upgrade
on the alternate boot disk. The option all indicates that
all the filesets contained in the directory you specified
(using option -l) must be installed to the alternate boot
disk.
Upgrading SF using an alternate disk
Upgrading SF on an alternate disk
Using SMIT interface
Start the SMIT menu and enter the required information at
the prompts:
# smitty alt_clone
■
Target disk to install: hdisk1
■
Fileset(s) to install: all
■
■
Directory or Device with images (full path of the directory
that contains the filesets to be upgraded):
/tmp/prod_name
ACCEPT new license agreements? yes
■
Set bootlist to boot from this disk on next reboot? yes
Press Enter to start the upgrade on the alternate disk. The
upgrade process takes some time.
2
Verify that the alternate disk is created:
# lspv |grep rootvg
hdisk0
hdisk1
3
0009710fa9c79877
0009710f0b90db93
rootvg
altinst_rootvg
Verify that the normal boot list includes the name of the alternate boot disk. By
default, the alternate disk installation process changes the boot list to enable
the system to boot from the alternate disk.
# bootlist -m normal -o
hdisk1
4
Restart all the nodes in the cluster. The boot environment on the alternate disk
is activated when you restart the nodes.
# shutdown -r
5
Start all the processes and ports.
# ./installsf -start
6
Verify the upgrade.
See “Verifying the upgrade” on page 98.
97
Upgrading SF using an alternate disk
Verifying the upgrade
Verifying the upgrade
To ensure that alternate disk installation has completed successfully, verify that the
system has booted from the alternate boot environment.
To verify the upgrade
1
Verify that the alternate boot environment is active:
# lspv |grep rootvg
hdisk0
hdisk1
2
0009710fa9c79877
0009710f0b90db93
old_rootvg
rootvg
active
Verify that the version of the upgraded filesets on the alternate boot disk is
6.0.100.0.
# lslpp -l | grep -i VRTS
Note: The VRTSsfcpi60 fileset still exists on the alternate boot disk. You need
to manually uninstall the package.
If you upgraded the operating system (TL or SP):
# oslevel -s
98
Chapter
15
Upgrading SF using
Network Install Manager
Alternate Disk Migration
This chapter includes the following topics:
■
Supported upgrade paths for SF using NIM ADM
■
Preparing to upgrade SF and the operating system using the nimadm utility
■
Preparing the installation bundle on the NIM server
■
Upgrading SF and the operating system using the nimadm utility
■
Verifying the upgrade performed using the NIM ADM utility
Supported upgrade paths for SF using NIM ADM
You can perform an upgrade of the product and the operating system using Network
Install Manager Alternate Disk Migration (NIM ADM).
The supported upgrade paths are as follows:
AIX version
AIX 5.3 and later
SF version
5.1 and later
Upgrading SF using Network Install Manager Alternate Disk Migration
Preparing to upgrade SF and the operating system using the nimadm utility
Preparing to upgrade SF and the operating system
using the nimadm utility
Complete the preparatory steps in the following procedure before you upgrade SF
and the operating system.
To prepare to upgrade SF and the operating system using the nimadm utility
1
Make sure that the SF installation media is available.
2
Check the status of the physical disks on your system.
Note: The alternate disk must have a physical identifier and must not contain
any mounted volume groups.
# lspv
Output similar to the following displays:
hdisk0
0009710fa9c79877
rootvg
hdisk1
0009710f0b90db93
None
active
If the alternate disk does not have a physical identifier, set the physical identifier
for the disk:
# chdev -l hdisk1 -a pv=yes
3
Make sure that the following filesets are installed on the NIM server and the
client: bos.alt_disk_install.boot_images, bos.alt_disk_install.rte
# lslpp -l -a | grep bos.alt_disk_install
Preparing the installation bundle on the NIM server
You need to prepare the installation bundle installp on the NIM server before
using nimadm to upgrade SF filesets. The following actions are executed on the
NIM server.
Note: Make sure that a NIM LPP_SOURCE is present on the NIM server.
100
Upgrading SF using Network Install Manager Alternate Disk Migration
Preparing the installation bundle on the NIM server
To prepare the installation bundle
1
Insert and mount the installation media.
2
Choose an LPP source:
# lsnim |grep -i lpp_source
LPP-6100-up2date resources lpp_source
3
Check that the NIM LPP_RESOURCE and corresponding SPOT are in healthy
state before starting the upgrade:
# nim -Fo check LPP_61TL7SP4
# nim -Fo check SPOT_61TL7SP4
4
Navigate to the product directory on the installation media and run the
installsf command to prepare the bundle resource:
# cd /opt/VRTS/install
# ./installsf -nim LPP-6100-up2date
The installation program copies the necessary filesets and patches to the LPP
resource directory.
5
Enter a name for the bundle, for example SF601.
6
Run the lsnim -l command to check that the installp_bundle resource is
created successfully.
# lsnim -l SF601
SF601:
class = resources
type = installp_bundle
Rstate = ready for use
prev_state = unavailable for use
location = /opt/VRTS/nim/SF601.bnd
alloc_count = 0
server = master
101
Upgrading SF using Network Install Manager Alternate Disk Migration
Upgrading SF and the operating system using the nimadm utility
Upgrading SF and the operating system using the
nimadm utility
This section provides instructions to upgrade SF and the operating system using
the nimadm utility. You may perform the steps manually or using the SMIT interface.
In the procedure examples, the primary or current boot environment is indicated
by hdisk0 and the alternate or inactive boot environment is indicated by hdisk1.
To upgrade Storage Foundation and the operating system using the nimadm utility
1
Clone the primary boot disk rootvg to an alternate disk using one of the
following methods:
Manual
Upgrade SF and the operating system by running the following
command on the NIM server:
# nimadm -l lpp_source -c nim_client \
-s spot_name -b bundle_name \
-d nimclient_altdisk_name -Y
For example:
# nimadm -l LPP-6100-up2date -c node1 \
-s spot-6100-up2date -b sf601 \
-d hdisk1 -Y
Where:
■
-l : Specifies the LPP_SOURCE
■
-c: Specifies the NIM client
■
-s: Specifies the SPOT resource
■
-b: Specifies SF bundle
■
-d: Specifies the alternate disk on which the installation is
performed
-Y: Specifies acceptance of all licenses
■
102
Upgrading SF using Network Install Manager Alternate Disk Migration
Upgrading SF and the operating system using the nimadm utility
Using SMIT interface
Start the SMIT menu:
# smit nimadm
Select the option Perform NIM Alternate Disk Migration.
Enter the required information at the prompts:
■
Target NIM Client: system1
■
NIM LPP_SOURCE resource: LPP-6100-up2date
■
NIM SPOT resource: SPOT-6100-up2date
■
Target disk(s) to install: hdisk1
■
Phase to execute: all
■
Set Client bootlist to alternate disk? yes
■
ACCEPT new license agreements? yes
Press Enter to start the upgrade on the alternate disk. The
upgrade process takes some time.
2
Verify that the alternate disk is created:
# lspv | grep rootvg
hdisk0
hdisk1
3
0009710fa9c79877
0009710f0b90db93
rootvg
altinst_rootvg
Verify that the normal boot list includes the name of the alternate boot disk. By
default, the alternate disk installation process changes the boot list to enable
the system to boot from the alternate disk.
# bootlist -m normal -o
hdisk1
4
Restart the system. The boot environment on the alternate disk is activated
when you restart the system.
# shutdown -r
5
Verify the upgrade.
See “Verifying the upgrade” on page 98.
Note: If the operating system version is incorrect, and the bos.txt.spell and
bos.txt.tfs filesets are missed, update these filesets manually through nim
6.1TL7SP4 lpp_source.
103
Upgrading SF using Network Install Manager Alternate Disk Migration
Verifying the upgrade performed using the NIM ADM utility
# oslevel -rl 6100-07
Fileset
Actual Level
Recommended ML
--------------------------------------------------------bos.txt.spell
5.3.12.0
6.1.6.0
bos.txt.tfs
5.3.12.0
6.1.6.0
To update the bos.txt.spell fileset manually, do the following:
smitty nim >> Perform NIM Software Installation and Maintenance Tasks >> Install
and Update Software >> Install Software >> Select corresponding LPP_SOURCE
>> * Software to Install >> Select bos.txt.spell
Follow the same procedure for the bos.txt.tfs fileset.
Verifying the upgrade performed using the NIM ADM
utility
To ensure that alternate disk installation has completed successfully, verify that all
the nodes have booted from the alternate boot environment and joined the cluster.
To verify the upgrade using the NIM ADM utility
1
Verify that the alternate boot environment is active:
# lspv | grep rootvg
hdisk0
hdisk1
2
0009710fa9c79877
0009710f0b90db93
old_rootvg
rootvg
active
Verify that the version of the upgraded filesets on the alternate boot disk is
6.0.100.0.
# lslpp -l | grep -i vrts
Note: The VRTSsfcpi60 fileset still exists on the alternate boot disk. You need
to manually uninstall the fileset.
If you upgraded the operating system:
# oslevel -s
104
Chapter
16
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.
Migrating from Storage Foundation Basic to Storage Foundation Standard
Migrating from Storage Foundation Basic to Storage Foundation Standard
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 Veritas 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 fileset 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 filesets to be installed, VRTSodm and
VRTSdbed. Press Enter to continue.
13 After installing the filesets 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.
106
Migrating from Storage Foundation Basic to Storage Foundation Standard
Migrating from Storage Foundation Basic to Storage Foundation Standard
107
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
17
Performing post-upgrade
tasks
This chapter includes the following topics:
■
Optional configuration steps
■
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 Veritas Volume Replicator (VVR) is configured, do the following steps in the
order shown:
■
Reattach the RLINKs.
■
Associate the SRL.
To upgrade VxFS Disk Layout versions and VxVM Disk Group versions, follow
the upgrade instructions.
Performing post-upgrade tasks
Post upgrade tasks for migrating the SFDB repository database
See “Upgrading VxVM disk group versions” on page 115.
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.0.1:
■
Rename startup script after upgrading from 5.0x and before migrating the SFDB
repository
See “After upgrading from 5.0.x and before migrating SFDB” on page 114.
■
Migrate from a 5.0x SFDB repository database to 6.0.1
See “Migrating from a 5.0 repository database to 6.0.1” on page 109.
■
Migrate from a 5.1 or 5.1SP1 repository database to 6.0.1
See “Migrating from a 5.1 or higher repository database to 6.0.1” on page 112.
Migrating from a 5.0 repository database to 6.0.1
To migrate from a 5.0 repository database to 6.0.1
1
Rename the startup script NO_S*vxdbms3 to S*vxdbms3.
See “After upgrading from 5.0.x and before migrating SFDB” on page 114.
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
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
109
Performing post-upgrade tasks
Post upgrade tasks for migrating the SFDB repository database
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.
110
Performing post-upgrade tasks
Post upgrade tasks for migrating the SFDB repository database
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
111
Performing post-upgrade tasks
Post upgrade tasks for migrating the SFDB repository database
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.
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.0.1
To migrate from a 5.0 repository database to 6.0.1
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.
112
Performing post-upgrade tasks
Post upgrade tasks for migrating the SFDB repository database
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
113
Performing post-upgrade tasks
Recovering VVR if automatic upgrade fails
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.
To begin using the Storage Foundation for Databases (SFDB) tools:
See Storage Foundation: Storage and Availability Management for Oracle Databases
After upgrading from 5.0.x and before migrating SFDB
When upgrading from SF version 5.0 or 5.0MP3 to SF 6.0.1 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:
/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.
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.
114
Performing post-upgrade tasks
Upgrading disk layout versions
Upgrading disk layout versions
In this release, you can create and mount only file systems with disk layout Version
7, 8, and 9. You can only local mount disk layout Version 6 only to upgrade to a
later disk layout version.
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.
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.
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 Veritas Storage Foundation
Administrator's Guide.
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.0.1, 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.0.1, 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.
115
Performing post-upgrade tasks
Updating variables
For more information about ISP disk groups, refer to the Veritas 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 Veritas Storage Foundation
Administrator's Guide.
Updating variables
In /etc/profile, update the PATH and MANPATH variables as needed.
MANPATH could include /opt/VRTS/man and PATH /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:
# vxdctl defaultdg diskgroup
See the Veritas 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 118.
116
Section
Post-installation tasks
■
Chapter 18. Verifying the SF installation
4
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 Veritas products
■
Checking Veritas Volume Manager processes
■
Checking Veritas File System installation
Verifying that the products were installed
Verify that the SF products are installed.
Use the lslpp command to check which filesets have been installed:
# lslpp -l | grep VRTS
The filesets should be in the COMMITTED state, as indicated by a C in the output:
VRTSaslapm
6.0.100.0
C
F
Array Support Libraries...
You can verify the version of the installed product. Use the following command:
# /opt/VRTS/install/installsf<version>
Where <version> is the specific release version.
See “About the Veritas installer” on page 22.
Use the following sections to further verify the product installation.
Verifying the SF installation
Installation log files
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 Veritas 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 filesets, and the status
(success or failure) of each fileset. 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 Veritas
products
After the installation and configuration is complete, the Veritas product installer
starts the processes that are used by the installed products. You can use the product
installer to stop or start the processes, if required.
119
Verifying the SF installation
Checking Veritas Volume Manager processes
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 Veritas installer” on page 22.
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 Veritas installer” on page 22.
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 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.
For more details on hot relocation, see Veritas Storage Foundation
Administrator's Guide.
120
Verifying the SF installation
Checking Veritas File System installation
Checking Veritas File System installation
After the Storage Foundation software has been successfully installed, you can
confirm successful Veritas File System installation.
To confirm the File System installation
◆
Use the lsvfs command as follows:
# lsvfs vxfs
Entries for these processes appear in output similar to the following:
vxfs 32 /sbin/helpers/vxfs /sbin/helpers/vxfs
121
Section
Uninstallation of SF
■
Chapter 19. Uninstalling Storage Foundation
■
Chapter 20. Uninstalling SF using response files
5
Chapter
19
Uninstalling Storage
Foundation
This chapter includes the following topics:
■
Preparing to uninstall a SF product
■
Removing the Replicated Data Set
■
Uninstalling SF filesets using the script-based installer
■
Uninstalling SF with the Veritas Web-based installer
■
Removing Storage Foundation products using SMIT
■
Removing the Storage Foundation for Databases (SFDB) repository after
removing the product
Preparing to uninstall a SF product
Complete the following preparations to uninstall a SF product.
Warning: Failure to follow the preparations that are outlined in this chapter can
result in loss of data.
To remove Veritas SF, complete the following preparations before the uninstallation:
■
Back up all VxFS file systems in full and move the files in all VxFS file systems
to native file systems backed with LVM logical volumes. Raw application data
stored in VxVM logical volumes must be moved to LVM logical volumes.
■
Remove all but one copy of file systems and databases.
Uninstalling Storage Foundation
Preparing to uninstall a SF product
■
Remove all but one plex from volumes that contain multiple plexes (mirrors).
To display a list of all volumes, use the command:
# vxprint -Ath
To remove a plex, use the command:
# vxplex -g diskgroup -o rm dis plex
■
If a remaining plex contains multiple subdisks, consolidate the subdisks into a
single subdisk using the commands:
# vxassist -g diskgroup mirror volume layout=contig
# vxplex -g diskgroup -o rm dis plex
Sufficient space on another disk is required for this operation to complete.
■
Modify /etc/filesystems to remove or change entries for VxFS file systems
that were moved to native file systems.
■
Move all data from volumes created from multiple regions of storage, including
striped or spanned volumes, onto a single disk or appropriate LVM logical
volume. This can be done using one of the following three methods:
■
Back up the system to tape or other media and recover the system from this.
■
Move volumes incrementally (evacuate) onto logical volumes. Evacuation
moves subdisks from the source disks to target disks. The evacuated disks
provide the initial free disk space for volumes to be moved to LVM volumes.
See “Moving volumes to physical disks” on page 124.
Moving volumes to physical disks
You can use the following steps to move data off of VxVM volumes.
To move data off of VxVM volumes
1
Evacuate as many disks as possible by using one of the following methods:
■
the "Remove a disk" option in vxdiskadm
■
the Veritas Enterprise Administrator
124
Uninstalling Storage Foundation
Preparing to uninstall a SF product
■
2
the vxevac script from the command line.
Remove the evacuated disks from Veritas Volume Manager control using the
following commands:
# vxdg -g diskgroup rmdisk disk_media_name
# /usr/lib/vxvm/bin/vxdiskunsetup -C disk_access_name
# vxdisk rm disk_access_name
For example:
# vxdg -g mydg rmdisk mydg01
# /usr/lib/vxvm/bin/vxdiskunsetup -C hdisk1
# vxdisk rm hdisk01
3
Decide which volume to move first. If the volume to be moved is mounted,
unmount it. 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 has been synchronized.
4
On the free disk space, create an LVM logical volume that is the same size as
the VxVM volume. If there is not enough free space for the logical volume, add
a new disk to the system for the first volume to be removed. For subsequent
volumes, you can use the free space generated by the removal of the first
volume.
5
Copy the data on the volume onto the newly created LVM logical volume using
the following command:
# dd if=/dev/vx/dsk/diskgroup/volume of=/dev/vgvol
where diskgroup is the name of a VxVM disk group, volume is the old volume
in that disk group, and vgvol is a newly created LVM volume.
If the volume contains a VxFS file system, the user data managed by VxFS in
the volume must be backed up or copied to a native AIX file system in an LVM
logical volume.
6
The entries in /etc/filesystems for volumes holding VxFS file systems, that
were copied to native file systems in step 5, must be modified according to the
change in step 5.
7
Mount the disk if the corresponding volume was previously mounted.
8
Remove the volume from VxVM using the following command:
# vxedit -g diskgroup -rf rm volume
125
Uninstalling Storage Foundation
Removing the Replicated Data Set
9
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 -g diskgroup -F "%sdnum" disk_media_name
10 If the return code is not 0, there are still some subdisks on this disk that must
be subsequently removed. If the return code is 0, remove the disk from VxVM
control using the following commands:
# vxdg -g diskgroup rmdisk disk_media_name
# vxdisk rm disk_access_name
11 Copy the data in the next volume to be removed to the newly created free
space.
12 Reboot the system after all volumes have been converted successfully. Verify
that no open volumes remain after the system reboot using the following
command:
# vxprint -Aht -e v_open
13 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 Veritas Volume Replicator, do not remove the Replicated
Data Set.
126
Uninstalling Storage Foundation
Removing the Replicated Data Set
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
127
Uninstalling Storage Foundation
Uninstalling SF filesets using the script-based installer
Uninstalling SF filesets using the script-based
installer
Use the following procedure to remove SF products.
Not all filesets 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.0.1 with a previous version of SF.
To shut down and remove the installed SF filesets
1
Disable DMP native support, if it is enabled. Run the following command to
disable DMP native support
# vxdmpadm settune dmp_native_support=off
# reboot
2
Comment out or remove any Veritas File System (VxFS) entries from the file
system table /etc/filesystems. Failing to remove these entries could result
in system boot problems later.
3
Unmount all mount points for VxFS file systems.
# umount /mount_point
4
If the VxVM fileset (VRTSvxvm) is installed, read and follow the uninstallation
procedures for VxVM.
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 ssh or rsh, use one of the following:
■
# ./uninstallsf<version> -rsh
■
# ./uninstallsf<version> -ssh
128
Uninstalling Storage Foundation
Uninstalling SF with the Veritas Web-based installer
See “About the Veritas installer” on page 22.
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 filesets are uninstalled.
The uninstall script creates log files and displays the location of the log files.
9
Most filesets have kernel components. In order to ensure complete removal,
a system reboot is recommended after all filesets have been removed.
Uninstalling SF with the Veritas Web-based installer
This section describes how to uninstall using the Veritas 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.0.1 with a previous version of SF.
To uninstall SF
1
Perform the required steps to save any data that you wish to preserve. For
example, take back-ups of configuration files.
2
Disable DMP native support, if it is enabled. Run the following command to
disable DMP native support
# vxdmpadm settune dmp_native_support=off
# reboot
3
Start the Web-based installer.
See “Starting the Veritas Web-based installer” on page 41.
4
On the Select a task and a product page, select Uninstall a Product from the
Task drop-down list.
5
Select Storage Foundation from the Product drop-down list, and click Next.
6
Indicate the systems on which to uninstall. Enter one or more system names,
separated by spaces. Click Next.
7
After the validation completes successfully, click Next to uninstall SF on the
selected system.
129
Uninstalling Storage Foundation
Removing Storage Foundation products using SMIT
8
If there are any processes running on the target system, the installer stops the
processes. Click Next.
9
After the installer stops the processes, the installer removes the products from
the specified system.
Click Next.
10 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.
11 Click Finish.
Most filesets have kernel components. In order to ensure their complete
removal, a system reboot is recommended after all the filesets have been
removed.
Removing Storage Foundation products using SMIT
Use the following procedure to remove Storage Foundation products using SMIT.
130
Uninstalling Storage Foundation
Removing Storage Foundation products using SMIT
To remove the filesets using SMIT
1
Stop the following SFCFSHA modules: VCS,VxFEN, ODM, GAB, and LLT.
Run the following commands to stop the SFCFSHA modules:
# hastop -all
# /etc/methods/glmkextadm unload
# /etc/rc.d/rc2.d/s99odm stop
# /etc/methods/gmskextadm unload
# /etc/init.d/vxfen.rc stop
# /etc/init.d/gab.rc stop
# /etc/init.d/llt.rc stop
Run the following commands to check if all the modules have been stopped:
# gabconfig -a
# ltconfig
2
Disable DMP native support, if it is enabled. Run the following command to
disable DMP native support
# vxdmpadm settune dmp_native_support=off
# reboot
3
Enter this command to invoke SMIT:
# smit
4
In SMIT, select Software Installation and Maintenance > Software
Maintenance and Utilities > Remove Installed Software.
5
Under the "SOFTWARE name" menu, press F4 or Esc-4 to list all software
installed on the system.
6
Enter "/" for Find, type "VRTS" to find all Veritas filesets, and select the filesets
that you want to remove.
131
Uninstalling Storage Foundation
Removing the Storage Foundation for Databases (SFDB) repository after removing the product
7
Reboot the system after removing all Storage Foundation filesets.
8
Depending on the choices that were made when Storage Foundation was
originally installed, you may find that not all of the listed Storage Foundation
filesets are installed on the system. You may also choose to remove the
VRTSvlic licensing fileset unless this is required by other Veritas software.
Removing the Storage Foundation for Databases
(SFDB) repository after removing the product
After removing the product, you can remove the SFDB repository file and any
backups.
Removing the SFDB repository file disables the SFDB tools.
To remove the SFDB repository
1
Identify the SFDB repositories created on the host.
# cat /var/vx/vxdba/rep_loc
2
Remove the directory identified by the location key.
3
Remove the repository location file.
# rm -rf /var/vx/vxdba/rep_loc
This completes the removal of the SFDB repository.
132
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 one of the cluster systems 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 Veritas installer” on page 22.
Uninstalling SF using response files
Response file variables to uninstall Storage Foundation
Response file variables to uninstall Storage
Foundation
Table 20-1 lists the response file variables that you can define to configure SF.
Table 20-1
Response file variables for uninstalling SF
Variable
Description
CFG{systems}
List of systems on which the product is to be installed or
uninstalled.
List or scalar: list
Optional or required: required
CFG{prod}
Defines the product to be installed or uninstalled.
List or scalar: scalar
Optional or required: required
CFG{opt}{keyfile}
Defines the location of an ssh keyfile that is used to
communicate with all remote systems.
List or scalar: scalar
Optional or required: optional
CFG{opt}{tmppath}
Defines the location where a working directory is created
to store temporary files and the filesets that are needed
during the install. The default location is /var/tmp.
List or scalar: scalar
Optional or required: optional
CFG{opt}{logpath}
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
CFG{opt}{uninstall}
Uninstalls SF filesets.
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.
134
Uninstalling SF using response files
Sample response file for SF uninstallation
our %CFG;
$CFG{opt}{redirect}=1;
$CFG{opt}{uninstall}=1;
$CFG{prod}="SF60";
$CFG{systems}=[ qw(thoropt89 thoropt90) ];
1;
135
Section
6
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. Changing NFS server major numbers for VxVM volumes
■
Appendix G. 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 Veritas Storage Foundation product scripts, except where otherwise noted.
See “About the Veritas installer” on page 22.
Table A-1
Available command line options
Commandline Option
Function
-allpkgs
Displays all filesets required for the specified
product. The filesets are listed in correct installation
order. The output can be used to create scripts for
command line installs, or for installations over a
network.
-comcleanup
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.
-configure
Configures the product after installation.
–hostfile full_path_to_file
Specifies the location of a file that contains a list
of hostnames on which to install.
Installation scripts
Installation script options
Table A-1
Available command line options (continued)
Commandline Option
Function
-installallpkgs
The -installallpkgs option is used to select
all filesets.
-installrecpkgs
The -installrecpkgsoption is used to select
the recommended filesets set.
–installminpkgs
The -installminpkgsoption is used to select
the minimum filesets set.
-ignorepatchreqs
The -ignorepatchreqs option is used to allow
installation or upgrading even if the prerequisite
packages or patches are missed on the system.
–keyfile ssh_key_file
Specifies a key file for secure shell (SSH) installs.
This option passes -i ssh_key_file to every
SSH invocation.
-license
Registers or updates product licenses on the
specified systems.
–logpath log_path
Specifies a directory other than
/opt/VRTS/install/logs as the location
where installer log files, summary files, and
response files are saved.
-makeresponsefile
Use the -makeresponsefile option only to
generate response files. No actual software
installation occurs when you use this option.
-minpkgs
Displays the minimal filesets required for the
specified product. The filesets are listed in correct
installation order. Optional filesets are not listed.
The output can be used to create scripts for
command line installs, or for installations over a
network. See allpkgs option.
-nim
Produces a NIM configuration file for installing with
NIM.
-nolic
Allows installation of product filesets without
entering a license key. Licensed features cannot
be configured, started, or used when this option is
specified.
138
Installation scripts
Installation script options
Table A-1
Available command line options (continued)
Commandline Option
Function
–pkginfo
Displays a list of filesets 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 filesets.
–pkgpath package_path
Designates the path of a directory that contains all
filesets to install. The directory is typically an
NFS-mounted location and must be accessible by
all specified installation systems.
–pkgset
Discovers and displays the fileset group (minimum,
recommended, all) and filesets that are installed
on the specified systems.
-pkgtable
Displays product's filesets in correct installation
order by group.
–postcheck
Checks for different HA and file system-related
processes, the availability of different ports, and
the availability of cluster-related service groups.
-precheck
Performs a preinstallation check to determine if
systems meet all installation requirements.
Symantec recommends doing a precheck before
installing a product.
–recpkgs
Displays the recommended filesets required for
the specified product. The filesets are listed in
correct installation order. Optional filesets are not
listed. The output can be used to create scripts for
command line installs, or for installations over a
network. See allpkgs option.
-redirect
Displays progress details without showing the
progress bar.
-requirements
The -requirements option displays required OS
version, required filesets and patches, file system
space, and other system requirements in order to
install the product.
139
Installation scripts
Installation script options
Table A-1
Available command line options (continued)
Commandline Option
Function
–responsefile response_file
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
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 154.
–serial
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.
-settunables
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.
-start
Starts the daemons and processes for the specified
product.
-stop
Stops the daemons and processes for the specified
product.
-timeout
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
140
Installation scripts
Installation script options
Table A-1
Available command line options (continued)
Commandline Option
Function
–tmppath tmp_path
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 filesets are copied on remote systems
before installation.
-tunables
Lists all supported tunables and create a tunables
file template.
-tunables_file tunables_file
Specify this option when you specify a tunables
file. The tunables file should include tunable
parameters.
-upgrade
Specifies that an existing version of the product
exists and you plan to upgrade it.
-version
Checks and reports the installed products and their
versions. Identifies the installed and missing
filesets and patches where applicable for the
product. Provides a summary that includes the
count of the installed and any missing filesets and
patches where applicable. Lists the installed
patches, hotfixes, and available updates for the
installed product if an Internet connection is
available.
141
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 143.
■
When you apply the tunables file with no other installer-related operations.
# ./installer -tunablesfile tunables_file_name -settunables [
system1 system2 ...]
Tunable files for installation
Setting tunables for an installation, configuration, or upgrade
See “Setting tunables with no other installer-related operations” on page 144.
■
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 145.
See “About response files” on page 21.
You must select the tunables that you want to use from this guide.
See “Tunables value parameter definitions” on page 147.
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 147.
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 146.
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.
6
Start the installer for the installation, configuration, or upgrade. For example:
# ./installer -tunablesfile /tmp/tunables_file
Where /tmp/tunables_file is the full path name for the tunables file.
143
Tunable files for installation
Setting tunables with no other installer-related operations
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 147.
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 146.
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.
144
Tunable files for installation
Setting tunables with an un-integrated response 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 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 147.
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 146.
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.
145
Tunable files for installation
Preparing the tunables file
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.
146
Tunable files for installation
Tunables value parameter definitions
See “Tunables value parameter definitions” on page 147.
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 Veritas Storage Foundation
and High Availability Solutions Tuning 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
Description
dmp_cache_open
(Veritas Dynamic Multi-Pathing) Whether the first open
on a device performed by an array support library (ASL)
is cached. This tunable must be set after Veritas Dynamic
Multi-Pathing is started.
dmp_daemon_count
(Veritas Dynamic Multi-Pathing) The number of kernel
threads for DMP administrative tasks. This tunable must
be set after Veritas Dynamic Multi-Pathing is started.
dmp_delayq_interval
(Veritas Dynamic Multi-Pathing) The time interval for
which DMP delays the error processing if the device is
busy. This tunable must be set after Veritas Dynamic
Multi-Pathing is started.
dmp_fast_recovery
(Veritas Dynamic Multi-Pathing) Whether DMP should
attempt to obtain SCSI error information directly from the
HBA interface. This tunable must be set after Veritas
Dynamic Multi-Pathing is started.
147
Tunable files for installation
Tunables value parameter definitions
Table B-1
Supported tunable parameters (continued)
Tunable
Description
dmp_health_time
(Veritas Dynamic Multi-Pathing) The time in seconds for
which a path must stay healthy. This tunable must be set
after Veritas Dynamic Multi-Pathing is started.
dmp_log_level
(Veritas Dynamic Multi-Pathing) The level of detail to
which DMP console messages are displayed. This
tunable must be set after Veritas Dynamic Multi-Pathing
is started.
dmp_low_impact_probe
(Veritas Dynamic Multi-Pathing) Whether the low impact
path probing feature is enabled. This tunable must be
set after Veritas Dynamic Multi-Pathing is started.
dmp_lun_retry_timeout
(Veritas Dynamic Multi-Pathing) The retry period for
handling transient errors. This tunable must be set after
Veritas Dynamic Multi-Pathing is started.
dmp_monitor_fabric
(Veritas Dynamic Multi-Pathing) Whether the Event
Source daemon (vxesd) uses the Storage Networking
Industry Association (SNIA) HBA API. This tunable must
be set after Veritas Dynamic Multi-Pathing is started.
dmp_monitor_osevent
(Veritas Dynamic Multi-Pathing) Whether the Event
Source daemon (vxesd) monitors operating system
events. This tunable must be set after Veritas Dynamic
Multi-Pathing is started.
dmp_monitor_ownership
(Veritas Dynamic Multi-Pathing) Whether the dynamic
change in LUN ownership is monitored. This tunable
must be set after Veritas Dynamic Multi-Pathing is
started.
dmp_native_support
(Veritas Dynamic Multi-Pathing) Whether DMP does
multi-pathing for native devices. This tunable must be
set after Veritas Dynamic Multi-Pathing is started.
dmp_path_age
(Veritas Dynamic Multi-Pathing) The time for which an
intermittently failing path needs to be monitored before
DMP marks it as healthy. This tunable must be set after
Veritas Dynamic Multi-Pathing is started.
148
Tunable files for installation
Tunables value parameter definitions
Table B-1
Supported tunable parameters (continued)
Tunable
Description
dmp_pathswitch_blks_shift
(Veritas 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. This tunable
must be set after Veritas Dynamic Multi-Pathing is
started.
dmp_probe_idle_lun
(Veritas Dynamic Multi-Pathing) Whether the path
restoration kernel thread probes idle LUNs. This tunable
must be set after Veritas Dynamic Multi-Pathing is
started.
dmp_probe_threshold
(Veritas Dynamic Multi-Pathing) The number of paths
will be probed by the restore daemon. This tunable must
be set after Veritas Dynamic Multi-Pathing is started.
dmp_restore_cycles
(Veritas Dynamic Multi-Pathing) The number of cycles
between running the check_all policy when the restore
policy is check_periodic. This tunable must be set after
Veritas Dynamic Multi-Pathing is started.
dmp_restore_interval
(Veritas Dynamic Multi-Pathing) The time interval in
seconds the restore daemon analyzes the condition of
paths. This tunable must be set after Veritas Dynamic
Multi-Pathing is started.
dmp_restore_policy
(Veritas Dynamic Multi-Pathing) The policy used by DMP
path restoration thread. This tunable must be set after
Veritas Dynamic Multi-Pathing is started.
dmp_restore_state
(Veritas Dynamic Multi-Pathing) Whether kernel thread
for DMP path restoration is started. This tunable must
be set after Veritas Dynamic Multi-Pathing is started.
dmp_retry_count
(Veritas Dynamic Multi-Pathing) The number of times a
path reports a path busy error consecutively before DMP
marks the path as failed. This tunable must be set after
Veritas Dynamic Multi-Pathing is started.
dmp_scsi_timeout
(Veritas Dynamic Multi-Pathing) The timeout value for
any SCSI command sent via DMP. This tunable must be
set after Veritas Dynamic Multi-Pathing is started.
dmp_sfg_threshold
(Veritas Dynamic Multi-Pathing) The status of the
subpaths failover group (SFG) feature. This tunable must
be set after Veritas Dynamic Multi-Pathing is started.
149
Tunable files for installation
Tunables value parameter definitions
Table B-1
Supported tunable parameters (continued)
Tunable
Description
dmp_stat_interval
(Veritas Dynamic Multi-Pathing) The time interval
between gathering DMP statistics. This tunable must be
set after Veritas Dynamic Multi-Pathing is started.
max_diskq
(Veritas File System) Specifies the maximum disk queue
generated by a single file. The installer sets only the
system default value of max_diskq. Refer to the
tunefstab(4) manual page for setting this tunable for a
specified block device.
read_ahead
(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 sets
only the system default value of read_ahead. Refer to
the tunefstab(4) manual page for setting this tunable for
a specified block device.
read_nstream
(Veritas File System) The number of parallel read
requests of size read_pref_io that can be outstanding at
one time. The installer sets only the system default value
of read_nstream. Refer to the tunefstab(4) manual page
for setting this tunable for a specified block device.
read_pref_io
(Veritas File System) The preferred read request size.
The installer sets only the system default value of
read_pref_io. Refer to the tunefstab(4) manual page for
setting this tunable for a specified block device.
vol_checkpt_default
(Veritas File System) Size of VxVM storage checkpoints
(sectors). This tunable requires system reboot to take
effect.
vol_cmpres_enabled
(Veritas Volume Manager) Allow enabling compression
for VERITAS Volume Replicator.
vol_cmpres_threads
(Veritas Volume Manager) Maximum number of
compression threads for VERITAS Volume Replicator.
vol_default_iodelay
(Veritas Volume Manager) Time to pause between I/O
requests from VxVM utilities (10ms units). This tunable
requires system reboot to take effect.
150
Tunable files for installation
Tunables value parameter definitions
Table B-1
Supported tunable parameters (continued)
Tunable
Description
vol_fmr_logsz
(Veritas Volume Manager) Maximum size of bitmap Fast
Mirror Resync uses to track changed blocks (KBytes).
This tunable requires system reboot to take effect.
vol_max_adminio_poolsz
(Veritas Volume Manager) Maximum amount of memory
used by VxVM admin I/O's (bytes). This tunablle rquires
system reboot to take effect.
vol_max_nmpool_sz
(Veritas Volume Manager) Maximum name pool size
(bytes).
vol_max_rdback_sz
(Veritas Volume Manager) Storage Record readback
pool maximum (bytes).
vol_max_wrspool_sz
(Veritas Volume Manager) Maximum memory used in
clustered version of VERITAS Volume Replicator (bytes).
vol_maxio
(Veritas Volume Manager) Maximum size of logical VxVM
I/O operations (sectors). This tunable requires system
reboot to take effect.
vol_maxioctl
(Veritas Volume Manager) Maximum size of data passed
into the VxVM ioctl calls (bytes). This tunable requires
system reboot to take effect.
vol_maxparallelio
(Veritas Volume Manager) Number of I/O operations
vxconfigd can request at one time. This tunable requires
system reboot to take effect.
vol_maxspecialio
(Veritas Volume Manager) Maximum size of a VxVM I/O
operation issued by an ioctl call (sectors). This tunable
requires system reboot to take effect.
vol_min_lowmem_sz
(Veritas Volume Manager) Low water mark for memory
(bytes).
vol_nm_hb_timeout
(Veritas Volume Manager) Veritas Volume Replicator
timeout value (ticks).
vol_rvio_maxpool_sz
(Veritas Volume Manager) Maximum memory requested
by VERITAS Volume Replicator (bytes).
vol_stats_enable
(Veritas Volume Manager) Enable VxVM I/O stat
collection.
151
Tunable files for installation
Tunables value parameter definitions
Table B-1
Supported tunable parameters (continued)
Tunable
Description
vol_subdisk_num
(Veritas Volume Manager) Maximum number of subdisks
attached to a single VxVM plex. This tunable requires
system reboot to take effect.
voldrl_max_drtregs
(Veritas Volume Manager) Maximum number of dirty
VxVM regions that can exist on a non-sequential DRL.
This tunable requires system reboot to take effect.
voldrl_max_seq_dirty
(Veritas Volume Manager) Maximum number of dirty
regions in sequential mode. This tunable requires system
reboot to take effect.
voldrl_min_regionsz
(Veritas Volume Manager) Minimum size of a VxVM Dirty
Region Logging (DRL) region (sectors). This tunable
requires system reboot to take effect.
voldrl_volumemax_drtregs
(Veritas Volume Manager) Max per volume dirty regions
in log-plex DRL.
voldrl_volumemax_drtregs_20
(Veritas Volume Manager) Max per volume dirty regions
in DCO version 20.
voldrl_dirty_regions
(Veritas Volume Manager) Number of regions cached
for DCO version 30.
voliomem_chunk_size
(Veritas Volume Manager) Size of VxVM memory
allocation requests (bytes). This tunable requires system
reboot to take effect.
voliomem_maxpool_sz
(Veritas Volume Manager) Maximum amount of memory
used by VxVM (bytes). This tunable requires system
reboot to take effect.
voliot_errbuf_dflt
(Veritas Volume Manager) Size of a VxVM error trace
buffer (bytes). This tunable requires system reboot to
take effect.
voliot_iobuf_default
(Veritas Volume Manager) Default size of a VxVM I/O
trace buffer (bytes). This tunable requires system reboot
to take effect.
voliot_iobuf_limit
(Veritas Volume Manager) Maximum total size of all
VxVM I/O trace buffers (bytes). This tunable requires
system reboot to take effect.
152
Tunable files for installation
Tunables value parameter definitions
Table B-1
Supported tunable parameters (continued)
Tunable
Description
voliot_iobuf_max
(Veritas Volume Manager) Maximum size of a VxVM I/O
trace buffer (bytes). This tunable requires system reboot
to take effect.
voliot_max_open
(Veritas Volume Manager) Maximum number of VxVM
trace channels available for vxtrace commands. This
tunable requires system reboot to take effect.
volpagemod_max_memsz
(Veritas Volume Manager) Maximum paging module
memory used by Instant Snapshots (Kbytes).
volraid_rsrtransmax
(Veritas Volume Manager) Maximum number of VxVM
RAID-5 transient reconstruct operations in parallel. This
tunable requires system reboot to take effect.
vx_bc_bufhwm
(Veritas File System) VxFS metadata buffer cache high
water mark. This tunable requires system reboot to take
effect.
vxfs_ninode
(Veritas File System) Number of entries in the VxFS inode
table. This tunable requires system reboot to take effect.
write_nstream
(Veritas File System) The number of parallel write
requests of size write_pref_io that can be outstanding at
one time. The installer sets only the system default value
of write_nstream. Refer to the tunefstab(4) manual page
for setting this tunable for a specified block device.
write_pref_io
(Veritas File System) The preferred write request size.
The installer sets only the system default value of
write_pref_io. Refer to the tunefstab(4) manual page for
setting this tunable for a specified block device.
153
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 and passwordless ssh
■
Restarting the ssh session
■
Enabling rsh for AIX
About configuring secure shell or remote shell
communication modes before installing products
Establishing communication between nodes is required to install Veritas 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 Veritas 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.
This section contains an example of how to set up ssh password free communication.
The example sets up ssh between a source system (system1) that contains the
installation directories, and a target system (system2). This procedure also applies
to multiple target systems.
Configuring the secure shell or the remote shell for communications
Manually configuring and passwordless ssh
155
Note: The script- and Web-based installers support establishing passwordless
communication for you.
Manually configuring and 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.
Figure C-1
Creating the DSA key pair and appending it to target systems
Source System: system1
Private
Key
Target System: system2
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.
Configuring the secure shell or the remote shell for communications
Manually configuring and passwordless ssh
To create the DSA key pair
1
On the source system (system1), log in as root, and navigate to the root
directory.
system1 # cd /
2
Make sure the /.ssh directory is on all the target installation systems (system2
in this example). If that directory is not present, create it on all the target systems
and set the write permission to root only:
system2 # mkdir /.ssh
Change the permissions of this directory, to secure it.
system2 # chmod go-w /.ssh
3
To generate a DSA key pair on the source system, type the following command:
system1 # 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 (//.ssh/id_dsa):
4
Press Enter to accept the default location of /.ssh/id_dsa.
5
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.
156
Configuring the secure shell or the remote shell for communications
Manually configuring and passwordless ssh
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 (system1), move the public key to a temporary file on
the target system (system2).
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:
system1 # sftp system2
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 system2 ...
The authenticity of host 'system2 (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 'system2,10.182.00.00'
(DSA) to the list of known hosts.
root@system2 password:
3
Enter the root password of system2.
4
At the sftp prompt, type the following command:
sftp> put /.ssh/id_dsa.pub
The following output is displayed:
Uploading /.ssh/id_dsa.pub to /id_dsa.pub
5
To quit the SFTP session, type the following command:
sftp> quit
157
Configuring the secure shell or the remote shell for communications
Manually configuring and passwordless ssh
6
To begin the ssh session on the target system (system2 in this example), type
the following command on system1:
system1 # ssh system2
Enter the root password of system2 at the prompt:
password:
7
After you log in to system2, enter the following command to append the
id_dsa.pub file to the authorized_keys file:
system2 # cat /id_dsa.pub >> /.ssh/authorized_keys
8
After the id_dsa.pub public key file is copied to the target system (system2),
and added to the authorized keys file, delete it. To delete the id_dsa.pub public
key file, enter the following command on system2:
system2 # rm /id_dsa.pub
9
To log out of the ssh session, enter the following command:
system2 # exit
10 When you install from a source system that is also an installation target, also
add the local system id_dsa.pub key to the local authorized_keys file. The
installation can fail if the installation source system is not authenticated.
To add the local system id_dsa.pub key to the local authorized_keys file,
enter the following command:
system1 # cat /.ssh/id_dsa.pub >> /.ssh/authorized_keys
11 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:
system1 # exec /usr/bin/ssh-agent $SHELL
system1 # ssh-add
Identity added: //.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.
158
Configuring the secure shell or the remote shell for communications
Restarting the ssh session
To verify that you can connect to a target system
1
On the source system (system1), enter the following command:
system1 # ssh -l root system2 uname -a
where system2 is the name of the target system.
2
The command should execute from the source system (system1) to the target
system (system2) without the system requesting a passphrase or password.
3
Repeat this procedure for each target system.
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 (system1), bring the private key into the shell
environment.
system1 # exec /usr/bin/ssh-agent $SHELL
2
Make the key globally available for the user root
system1 # ssh-add
Enabling rsh for AIX
To enable rsh, create a /.rhosts file on each target system. Then add a line to
the file specifying the full domain name of the source system. For example, add
the line:
sysname.domainname.com root
Change permissions on the /.rhosts file to 600 by typing the following command:
# chmod 600 /.rhosts
159
Configuring the secure shell or the remote shell for communications
Enabling rsh for AIX
After you complete an installation procedure, delete the .rhosts file from each
target system to ensure security:
# rm -f /.rhosts
160
Appendix
D
Storage Foundation
components
This appendix includes the following topics:
■
Storage Foundation installation filesets
■
Veritas Storage Foundation obsolete and reorganized installation filesets
Storage Foundation installation filesets
Table D-1 shows the fileset name and contents for each English language fileset
for Storage Foundation. The table also gives you guidelines for which filesets to
install based whether you want the minimum, recommended, or advanced
configuration.
When you install all Storage Foundation and Veritas Cluster Server (VCS) filesets,
the combined functionality is called Storage Foundation and High Availability.
Table D-1
Storage Foundation filesets
filesets
Contents
Configuration
VRTSaslapm
Veritas Array Support Library (ASL)
Minimum
and Array Policy Module(APM) binaries
Required for the support and
compatibility of various storage arrays.
VRTSperl
Perl 5.14.2 for Veritas
Minimum
VRTSveki
Veritas Kernel Interface
Minimum
Contains a common set of modules
that other Veritas drivers use.
Storage Foundation components
Storage Foundation installation filesets
Table D-1
Storage Foundation filesets (continued)
filesets
Contents
Configuration
VRTSvlic
Veritas License Utilities
Minimum
Installs the license key layout files
required to decode the Storage
Foundation license keys. Provides the
standard license key utilities vxlicrep,
vxlicinst, and vxlictest.
VRTSvxfs
Veritas File System binaries
Minimum
Required for VxFS file system support.
VRTSvxvm
Veritas Volume Manager binaries,
Minimum
scripts, and utilities. Required for VxVM
volume manager support.
VRTSdbed
Veritas Storage Foundation for
Databases
Recommended
VRTSob
Veritas Enterprise Administrator
Recommended
VRTSodm
Veritas ODM Driver for VxFS
Recommended
Veritas Extension for Oracle Disk
Manager is a custom storage interface
designed specifically for Oracle9i and
10g. Oracle Disk Manager allows
Oracle 9i and 10g to improve
performance and manage system
bandwidth.
162
Storage Foundation components
Storage Foundation installation filesets
Table D-1
Storage Foundation filesets (continued)
filesets
Contents
Configuration
VRTSsfcpi601
Veritas Storage Foundation Common
Product Installer
Minimum
The Storage Foundation Common
Product installer fileset contains the
installer libraries and product scripts
that perform the following:
■
installation
■
configuration
■
upgrade
■
uninstallation
■
adding nodes
■
removing nodes
■
etc.
You can use these script to simplify the
native operating system installations,
configurations, and upgrades.
VRTSsfmh
Veritas Storage Foundation Managed Recommended
Host
Veritas Storage Foundation Managed
Host is now called Veritas Operations
Manager (VOM).
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
package on a server, and add this
managed host to the Central Server.
The VRTSsfmcs package is not part of
this release. You can download it
separately from:
http://www.symantec.com/veritas-operations-manager
VRTSspt
Veritas Software Support Tools
Recommended
163
Storage Foundation components
Veritas Storage Foundation obsolete and reorganized installation filesets
Table D-1
Storage Foundation filesets (continued)
filesets
Contents
Configuration
VRTSfssdk
Veritas File System Software
Developer Kit
All
For VxFS APIs, the fileset contains the
public Software Developer Kit
(headers, libraries, and sample code).
It is required if some user programs
use VxFS APIs.
Veritas Storage Foundation obsolete and reorganized
installation filesets
Table D-2 lists the filesets that are obsolete or reorganized for Storage Foundation.
Table D-2
Veritas Storage Foundation obsolete and reorganized filesets
fileset
Description
Obsolete and reorganized for 6.0.1
VRTSat
Obsolete
Obsolete and reorganized for 5.1
Infrastructure
SYMClma
Obsolete
VRTSaa
Included in VRTSsfmh
VRTSccg
Included in VRTSsfmh
VRTSdbms3
Obsolete
VRTSicsco
Obsolete
VRTSjre
Obsolete
VRTSjre15
Obsolete
VRTSmh
Included in VRTSsfmh
VRTSobc33
Obsolete
VRTSobgui
Obsolete
164
Storage Foundation components
Veritas Storage Foundation obsolete and reorganized installation filesets
Table D-2
Veritas Storage Foundation obsolete and reorganized filesets
(continued)
fileset
Description
VRTSpbx
Obsolete
VRTSsfm
Obsolete
VRTSweb
Obsolete
Product filesets
VRTSacclib
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, the existing VRTSacclib is
uninstalled and a new VRTSacclib is
installed.
For uninstallation, VRTSacclib is not
uninstalled.
VRTSalloc
Obsolete
VRTScmccc
Obsolete
VRTScmcs
Obsolete
VRTScscm
Obsolete
VRTScscw
Obsolete
VRTScsocw
Obsolete
VRTScssim
Obsolete
VRTScutil
Obsolete
VRTSd2gui
Included in VRTSdbed
VRTSdb2ed
Included in VRTSdbed
VRTSdbcom
Included in VRTSdbed
VRTSdbed
Included in VRTSdbed
VRTSdcli
Obsolete
165
Storage Foundation components
Veritas Storage Foundation obsolete and reorganized installation filesets
Table D-2
Veritas Storage Foundation obsolete and reorganized filesets
(continued)
fileset
Description
VRTSddlpr
Obsolete
VRTSdsa
Obsolete
VRTSfsman
Included in the product's main fileset.
VRTSfsmnd
Included in the product's main fileset.
VRTSfspro
Included in VRTSsfmh
VRTSgapms
Obsolete
VRTSmapro
Included in VRTSsfmh
VRTSorgui
Obsolete
VRTSvail
Obsolete
VRTSvcsdb
Included in VRTSvcsea
VRTSvcsor
Included in VRTSvcsea
VRTSvcsvr
Included in VRTSvcs
VRTSvdid
Obsolete
VRTSvmman
Included in the product's main fileset.
VRTSvmpro
Included in VRTSsfmh
VRTSvrpro
Included in VRTSob
VRTSvrw
Obsolete
VRTSvxmsa
Obsolete
Documentation
All Documentation filesets obsolete
166
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
■
Troubleshooting an installation on AIX
■
Incorrect permissions for root on remote system
■
Resource temporarily unavailable
■
Inaccessible system
■
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
Troubleshooting an installation on AIX
168
WARNING V-365-1-1 This host is not entitled to run Veritas Storage
Foundation/Veritas 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'
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 Veritas product license keys” on page 29.
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
Troubleshooting an installation on AIX
Save a copy of /var/adm/ras/errtmplt and /etc/trcfmt files before you install
the product. If the filesets fail to install due to the template file is corrupted
error message, replace /var/adm/ras/errtmplt file and /etc/trcfmt file with the
ones that you had saved, uninstall all the filesets installed.
See “Preparing to uninstall a SF product” on page 123.
Then reinstall.
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:
Troubleshooting installation issues
Resource temporarily unavailable
'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 154.
Note: Remove remote shell permissions after completing the SF installation and
configuration.
Resource temporarily unavailable
If the installation fails with the following error message on the console:
fork() failed: Resource temporarily unavailable
169
Troubleshooting installation issues
Inaccessible system
The value of maximum number of processes allowed per user may not be large
enough. This kernel attribute is a tunable and can be changed on any node of the
cluster.
To determine the current value of "Maximum number of PROCESSES allowed per
user", enter:
# lsattr -H -E -l sys0 -a maxuproc
To see the default value of this tunable and its valid range of values, enter:
# odmget -q "attribute=maxuproc" PdAt
If necessary, you can change the value of the tunable using the smitty interface:
# smitty chgsys
You can also directly change the CuAt class using the following command:
# chdev -l sys0 -a maxuproc=600
Increasing the value of the parameter takes effect immediately; otherwise the change
takes effect after a reboot.
See the smitty and chdev manual pages.
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 AIX 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.
170
Troubleshooting installation issues
Troubleshooting the webinstaller
171
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
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
Changing NFS server major
numbers for VxVM volumes
This appendix includes the following topics:
■
Changing NFS server major numbers for VxVM volumes
Changing NFS server major numbers for VxVM
volumes
In a VCS cluster, block devices providing NFS service must have the same major
and minor numbers on each cluster node. Major numbers identify required device
drivers (such as AIX partition or VxVM volume). Minor numbers identify the specific
devices themselves. NFS also uses major and minor numbers to identify the
exported file system. Major and minor numbers must be verified to ensure that the
NFS identity for the file system is the same when exported from each node.
Use the haremajor command to determine and reassign the major number that a
system uses for shared VxVM volume block devices. For Veritas Volume Manager,
the major number is set to the vxio driver number. To be highly available, each
NFS server in a VCS cluster must have the same vxio driver number, or major
number.
To list the major number currently in use on a system
◆
Use the command:
# haremajor -v
55
Run this command on each cluster node. If major numbers are not the same on
each node, you must change them on the nodes so that they are identical.
Changing NFS server major numbers for VxVM volumes
Changing NFS server major numbers for VxVM volumes
To list the available major numbers for a system
◆
Use the command:
# haremajor -a
54,56..58,60,62..
The output shows the numbers that are not in use on the system where the
command is issued.
To reset the major number on a system
◆
You can reset the major number to an available number on a system. For
example, to set the major number to 75 type:
# haremajor -s 75
173
Appendix
G
Compatability issues when
installing Storage
Foundation with other
products
This appendix includes the following topics:
■
Installing, uninstalling, or upgrading Storage Foundation products when other
Veritas 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 Veritas products
are present
Installing Storage Foundation when other Veritas 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
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 SFM or VOM
Central Server is present, the installer skips the VRTSsfmh upgrade and leaves
the SFM Central Server and Managed Host filesets as is.
■
When uninstalling Storage Foundation products where SFM or VOM Central
Server is present, the installer does not uninstall VRTSsfmh.
■
When you install or upgrade Storage Foundation products where SFM or 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.
175
Index
C
T
configuring
rsh 32
ssh 32
tunables file
about setting parameters 142
parameter definitions 147
preparing 146
setting for configuration 143
setting for installation 143
setting for upgrade 143
setting parameters 146
setting with no other operations 144
setting with un-integrated response file 145
D
deinstalling the Volume Manager 123
I
Installing
SF with the Web-based installer 43
M
migrating
from Storage Foundation Basic to Storage
Foundation Standard 105
mounting
software disc 33
P
planning to upgrade VVR 74
preinstallation 74
U
upgrading VVR
from 4.0 75
planning 74
V
Veritas Operations Manager 16
vradmin
delpri 127
stoprep 127
VVR 4.0
planning an upgrade from 75
R
removing
the Replicated Data Set 126
Replicated Data Set
removing the 126
rsh
configuration 32
S
ssh
configuration 32
Storage Foundation Basic to Storage Foundation
Standard
migrating 105
W
Web-based installer 43
Download PDF
Similar pages