Storage Foundation for Sybase ASE CE 7.4.1 Configuration and Upgrade Guide - Linux
- Section I. Configuring SF Sybase ASE CE
- Preparing to configure SF Sybase CE
- Configuring SF Sybase CE
- About configuring SF Sybase CE
- Configuring the SF Sybase CE components using the script-based installer
- Configuring the SF Sybase CE cluster
- Configuring the cluster name
- Configuring private heartbeat links
- Configuring the virtual IP of the cluster
- Configuring SF Sybase CE in secure mode
- Configuring a secure cluster node by node
- Adding VCS users
- Configuring SMTP email notification
- Configuring SNMP trap notification
- Configuring global clusters
- Configuring the SF Sybase CE cluster
- Configuring SF Sybase CE clusters for data integrity
- Setting up disk-based I/O fencing using installer
- Performing an automated SF Sybase CE configuration
- Performing an automated I/O fencing configuration using response files
- Configuring a cluster under VCS control using a response file
- Section II. Post-installation and configuration tasks
- Section III. Upgrade of SF Sybase CE
- Planning to upgrade SF Sybase CE
- Performing a full upgrade of SF Sybase CE using the product installer
- Performing an automated full upgrade of SF Sybase CE using response files
- Performing a phased upgrade of SF Sybase CE
- About phased upgrade
- Performing a phased upgrade of SF Sybase CE from version 6.2.1 and later release
- Step 1: Performing pre-upgrade tasks on the first half of the cluster
- Step 2: Upgrading the first half of the cluster
- Step 3: Performing pre-upgrade tasks on the second half of the cluster
- Step 4: Performing post-upgrade tasks on the first half of the cluster
- Step 5: Upgrading the second half of the cluster
- Step 6: Performing post-upgrade tasks on the second half of the cluster
- Performing a rolling upgrade of SF Sybase CE
- Performing post-upgrade tasks
- Section IV. Installation and upgrade of Sybase ASE CE
- Installing, configuring, and upgrading Sybase ASE CE
- Before installing Sybase ASE CE
- Preparing for local mount point on VxFS for Sybase ASE CE binary installation
- Preparing for shared mount point on CFS for Sybase ASE CE binary installation
- Installing Sybase ASE CE software
- Preparing to create a Sybase ASE CE cluster
- Creating the Sybase ASE CE cluster
- Preparing to configure the Sybase instances under VCS control
- Configuring a Sybase ASE CE cluster under VCS control using the SF Sybase CE installer
- Upgrading Sybase ASE CE
- Installing, configuring, and upgrading Sybase ASE CE
- Section V. Adding and removing nodes
- Adding a node to SF Sybase CE clusters
- About adding a node to a cluster
- Before adding a node to a cluster
- Adding the node to a cluster manually
- Starting Veritas Volume Manager (VxVM) on the new node
- Configuring cluster processes on the new node
- Setting up the node to run in secure mode
- Starting fencing on the new node
- Configuring Cluster Volume Manager (CVM) and Cluster File System (CFS) on the new node
- After adding the new node
- Configuring the ClusterService group for the new node
- Adding a node to a cluster using the Veritas InfoScale installer
- Adding the new instance to the Sybase ASE CE cluster
- Removing a node from SF Sybase CE clusters
- Adding a node to SF Sybase CE clusters
- Section VI. Configuration of disaster recovery environments
- Section VII. Installation reference
- Appendix A. Installation scripts
- Appendix B. Sample installation and configuration values
- Appendix C. Tunable files for installation
- 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 D. Configuration files
- About sample main.cf files
- Sample main.cf files for Sybase ASE CE configurations
- Sample main.cf for a basic Sybase ASE CE cluster configuration under VCS control with shared mount point on CFS for Sybase binary installation
- Sample main.cf for a basic Sybase ASE CE cluster configuration with local mount point on VxFS for Sybase binary installation
- Sample main.cf for a primary CVM VVR site
- Sample main.cf for a secondary CVM VVR site
- Appendix E. Configuring the secure shell or the remote shell for communications
- Appendix F. High availability agent information
Using Install Bundles to simultaneously install or upgrade full releases (base, maintenance, rolling patch), and individual patches
Beginning with version 6.2.1, you can easily install or upgrade your systems directly to a base, maintenance, patch level or a combination of multiple patches and packages together in one step using Install Bundles. With Install Bundles, the installer has the ability to merge so that customers can install or upgrade directly to maintenance or patch levels in one execution. The various scripts, RPMs, and patch components are merged, and multiple releases are installed together as if they are one combined release. You do not have to perform two or more install actions to install or upgrade systems to maintenance levels or patch levels.
Releases are divided into the following categories:
Table: Release Levels
Level | Content | Form factor | Applies to | Release types | Download location |
|---|---|---|---|---|---|
Base | Features | RPMs | All products | Major, minor, Service Pack (SP), Platform Release (PR) | FileConnect |
Maintenance | Fixes, new features | RPMs | All products | Maintenance Release (MR), Rolling Patch (RP) | Veritas Services and Operations Readiness Tools (SORT) |
Patch | Fixes | RPMs | Single product | P-Patch, Private Patch, Public patch | SORT, Support site |
When you install or upgrade using Install Bundles:
Veritas InfoScale products are discovered and assigned as a single version to the maintenance level. Each system can also have one or more patches applied.
Base releases are accessible from FileConnect that requires customer serial numbers. Maintenance and patch releases can be automatically downloaded from SORT.
Patches can be installed using automated installers from the 6.2.1 version or later.
Patches can now be detected to prevent upgrade conflict. Patch releases are not offered as a combined release. They are only available from Veritas Technical Support on a need basis.
You can use the -base_path and -patch_path options to import installation code from multiple releases. You can find RPMs and patches from different media paths, and merge RPM and patch definitions for multiple releases. You can use these options to use new task and phase functionality to correctly perform required operations for each release component. You can install the RPMs and patches in defined phases using these options, which helps you when you want to perform a single start or stop process and perform pre and post operations for all level in a single operation.
Four possible methods of integration exist. All commands must be executed from the highest base or maintenance level install script.
In the example below:
7.4.1 is the base version
7.4.1.1 is the maintenance version
7.4.1.1.100 is the patch version for 7.4.1.1
7.4.1.0.100 is the patch version for 7.4.1
Base + maintenance:
This integration method can be used when you install or upgrade from a lower version to 7.4.1.1.
Enter the following command:
# installmr -base_path <path_to_base>
Base + patch:
This integration method can be used when you install or upgrade from a lower version to 7.4.1.0.100.
Enter the following command:
# installer -patch_path <path_to_patch>
Maintenance + patch:
This integration method can be used when you upgrade from version 7.4.1 to 7.4.1.1.100.
Enter the following command:
# installmr -patch_path <path_to_patch>
Base + maintenance + patch:
This integration method can be used when you install or upgrade from a lower version to 7.4.1.1.100.
Enter the following command:
# installmr -base_path <path_to_base> -patch_path <path_to_patch>
Note:
From the 6.1 or later release, you can add a maximum of five patches using -patch_path <path_to_patch> -patch2_path <path_to_patch> ... -patch5_path <path_to_patch>