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
- Configuring the SF Sybase CE components using the script-based installer
- Configuring the SF Sybase CE cluster
- Configuring SF Sybase CE in secure mode
- Configuring a secure cluster node by node
- 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
- Performing a phased upgrade of SF Sybase CE from version 6.2.1 and later release
- 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
- Preparing to configure the Sybase instances under VCS control
- Installing, configuring, and upgrading Sybase ASE CE
- Section V. Adding and removing nodes
- Adding a node to SF Sybase CE clusters
- Adding the node to a cluster manually
- Setting up the node to run in secure mode
- 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
- Appendix D. Configuration files
- Sample main.cf files for Sybase ASE CE configurations
- Appendix E. Configuring the secure shell or the remote shell for communications
- Appendix F. High availability agent information
Adding a node to a cluster using the Veritas InfoScale installer
You can add a node to a cluster using the -addnode option with the Veritas InfoScale installer.
The Veritas InfoScale installer performs the following tasks:
Verifies that the node and the existing cluster meet communication requirements.
Verifies the products and RPMs installed but not configured on the new node.
Discovers the network interfaces on the new node and checks the interface settings.
Creates the following files on the new node:
/etc/llttab
/etc/VRTSvcs/conf/sysname
Updates and copies the following files to the new node from the existing node:
/etc/llthosts
/etc/gabtab
/etc/VRTSvcs/conf/config/main.cf
Copies the following files from the existing cluster to the new node:
/etc/vxfenmode
/etc/vxfendg
/etc/vx/.uuids/clusuuid
/etc/sysconfig/llt
/etc/sysconfig/gab
/etc/sysconfig/vxfen
Configures fencing.
Adds the new node to the CVM, ClusterService service groups in the VCS configuration.
Note:
For other service groups configured under VCS, update the configuration for the new node manually.
Starts SF Sybase CE processes and configures CVM and CFS on the new node.
At the end of the process, the new node joins the SF Sybase CE cluster.
To add the node to an existing cluster using the installer
- Log in as the root user on one of the nodes of the existing cluster.
- Run the Veritas InfoScale installer with the -addnode option.
# cd /opt/VRTS/install
# ./installer -addnode
The installer displays the copyright message and the location where it stores the temporary installation logs.
- Enter the name of a node in the existing SF Sybase CE cluster.
The installer uses the node information to identify the existing cluster.
Enter the name of any one node of the InfoScale ENTERPRISE cluster where you would like to add one or more new nodes: sys1
- Review and confirm the cluster information.
- Enter the name of the systems that you want to add as new nodes to the cluster.
Enter the system names separated by spaces to add to the cluster: system3
Confirm if the installer prompts if you want to add the node to the cluster.
The installer checks the installed products and RPMs on the nodes and discovers the network interfaces.
- Enter the name of the network interface that you want to configure as the first private heartbeat link.
If there are IP addresses already configured on the interface, confirm whether you want to use the interface as the first private heartbeat link.
Enter the NIC for the first private heartbeat link on system3: [b,q,?] eth1
Enter the NIC for the second private heartbeat link on system3: [b,q,?] eth2
Note:
At least two private heartbeat links must be configured for high availability of the cluster.
- Depending on the number of LLT links configured in the existing cluster, configure additional private heartbeat links for the new node.
The installer verifies the network interface settings and displays the information.
- Review and confirm the information.
- If you have configured SMTP, SNMP, or the global cluster option in the existing cluster, you are prompted for the NIC information for the new node.
Enter the NIC for VCS to use on system3: eth3
The installer starts the SF Sybase CE processes and configures CVM and CFS on the new node. The new node is now part of the cluster.
To add the new node into the Sybase ASE CE cluster and database:
- Configure the following service groups manually to include the new node in the VCS configuration:
The binmnt group which contains the Sybase binaries
The Sybase group which contains:
The new instance on the added node
The database mounts where the database resides
The quorum mounts where the quorum device resides.
- Confirm that the new node has joined the SF Sybase CE cluster using lltstat -n and gabconfig -a commands.