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
Configuring disk-based I/O fencing using installer
Note:
The installer stops and starts SF Sybase CE to complete I/O fencing configuration. Make sure to unfreeze any frozen VCS service groups in the cluster for the installer to successfully stop SF Sybase CE.
To set up disk-based I/O fencing using the installer
- Start the installer with -fencing option.
# /opt/VRTS/install/installer -fencing
The installer starts with a copyright message and verifies the cluster information.
Note the location of log files which you can access in the event of any problem with the configuration process.
- Enter the host name of one of the systems in the cluster.
- Confirm that you want to proceed with the I/O fencing configuration at the prompt.
The program checks that the local node running the script can communicate with remote nodes and checks whether SF Sybase CE 7.4.1 is configured properly.
- Review the I/O fencing configuration options that the program presents. Type 1 to configure fencing in Sybase mode.
Select the fencing mechanism to be configured in this Application Cluster [1-3,b,q] 1
- Review the output as the configuration program checks whether VxVM is already started and is running.
If the check fails, configure and enable VxVM before you repeat this procedure.
If the check passes, then the program prompts you for the coordinator disk group information.
- Choose whether to use an existing disk group or create a new disk group to configure as the coordinator disk group.
The program lists the available disk group names and provides an option to create a new disk group. Perform one of the following:
To use an existing disk group, enter the number corresponding to the disk group at the prompt.
The program verifies whether the disk group you chose has an odd number of disks and that the disk group has a minimum of three disks.
To create a new disk group, perform the following steps:
Enter the number corresponding to the Create a new disk group option.
The program lists the available disks that are in the CDS disk format in the cluster and asks you to choose an odd number of disks with at least three disks to be used as coordinator disks.
Veritas recommends that you use three disks as coordination points for disk-based I/O fencing.
If the available VxVM CDS disks are less than the required, installer asks whether you want to initialize more disks as VxVM disks. Choose the disks you want to initialize as VxVM disks and then use them to create new disk group.
Enter the numbers corresponding to the disks that you want to use as coordinator disks.
Enter the disk group name.
- Verify that the coordinator disks you chose meet the I/O fencing requirements.
You must verify that the disks are SCSI-3 PR compatible using the vxfentsthdw utility and then return to this configuration program.
- After you confirm the requirements, the program creates the coordinator disk group with the information you provided.
- Verify and confirm the I/O fencing configuration information that the installer summarizes.
Review the output as the configuration program does the following:
Stops VCS and I/O fencing on each node.
Configures disk-based I/O fencing and starts the I/O fencing process.
Updates the VCS configuration file main.cf if necessary.
Copies the /etc/vxfenmode file to a date and time suffixed file /etc/vxfenmode-date-time. This backup file is useful if any future fencing configuration fails.
Updates the I/O fencing configuration file /etc/vxfenmode.
Starts VCS on each node to make sure that the SF Sybase CE is cleanly configured to use the I/O fencing feature.
- Review the output as the configuration program displays the location of the log files, the summary files, and the response files.
- Configure the Coordination Point Agent.
Do you want to configure Coordination Point Agent on the client cluster? [y,n,q] (y)
- Enter a name for the service group for the Coordination Point Agent.
Enter a non-existing name for the service group for Coordination Point Agent: [b] (vxfen) vxfen
- Set the level two monitor frequency.
Do you want to set LevelTwoMonitorFreq? [y,n,q] (y)
- Decide the value of the level two monitor frequency.
Enter the value of the LevelTwoMonitorFreq attribute: [b,q,?] (5)
Installer adds Coordination Point Agent and updates the main configuration file.
- Enable auto refresh of coordination points.
Do you want to enable auto refresh of coordination points if registration keys are missing on any of them? [y,n,q,b,?] (n)