VERITAS Cluster Server Enterprise Agent for Sybase

Transcription

1 VERITAS Cluster Server Enterprise Agent for Sybase Installation and Configuration Guide HP-UX January

2 Disclaimer The information contained in this publication is subject to change without notice. VERITAS Software Corporation makes no warranty of any kind with regard to this manual, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. VERITAS Software Corporation shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this manual. Copyright Copyright VERITAS Software Corporation. All rights reserved. VERITAS is a registered trademark of VERITAS Software Corporation in the US and other countries. The VERITAS logo and VERITAS Cluster Server are trademarks of VERITAS Software Corporation. All other trademarks or registered trademarks are the property of their respective owners. Printed in the USA, January VERITAS Software Corporation 1600 Plymouth St. Mountain View, CA Phone Fax

3 Contents Preface v Technical Support v For Customers Outside U.S. and Canada v Conventions vi Chapter 1. Installing and Configuring the Agent Version Numbers and Operating Systems About the Agent SQL Server Agent: Sybase Backup Server Agent: SybaseBk Prerequisites Additional Requirements $SYBASE_HOME Directory on Shared Disks Database Dbspaces Transparent TCP/IP Failover Long Pathname Limitation for $SYBASE_HOME Installing the Agent Software A Sample Sybase Configuration Configuring the Agent Sybase Resource Type Type Definition Sample Configuration SybaseBk Resource Type Type Definition iii

4 Sample Configuration Dependencies Among the Sybase and SybaseBk Resources Configuring the Sybase Agent With Cluster Manager Importing the SybaseTypes.cf File Adding the Sybase Group Using the Wizard Configuring Sybase Agent by Editing the Configuration Files Setting the Sybase Password Attribute Using a Soft Link to a $SYBASE_HOME Pathname Example, Replacing $SYBASE_HOME Pathname With a Soft Link Modifying the Agent Configuration Dynamic Configuration Database Tables Additional Monitoring To modify the secondary monitor configuration: Disabling the Agent Removing the Agent iv VCS Enterprise Agent for Sybase Installation and Configuration Guide

5 Preface This document provides instructions on how to install and configure the VERITAS Cluster Server Agent for Sybase. For information about VCS, refer to the VERITAS Cluster Server User s Guide. Technical Support For assistance with this VERITAS product, or for information regarding VERITAS service packages, contact Technical Support at (U.S. and Canada). You may also contact Technical Support via at support@veritas.com. For Customers Outside U.S. and Canada From Europe, the Middle East, or Asia, visit the Technical Support website at for a list of each country s contact information. v

6 Conventions Conventions Typeface courier courier (bold) italic italic Symbol Usage Computer output, files, attribute names, device names, and directories User input and commands, keywords in grammar syntax New terms, titles, emphasis Variables Usage % C shell prompt $ Bourne/Korn shell prompt # Superuser prompt (for all shells) vi VCS Enterprise Agent for Sybase Installation and Configuration Guide

7 Installing and Configuring the Agent 1 Welcome to the VERITAS Cluster Server (VCS) agent, version 1.3.1, for Sybase. This guide describes the agent for Sybase, its modes of operation and its attributes. It describes how to install and configure the agent. Version Numbers and Operating Systems The VCS enterprise agent for Sybase monitors Sybase Adaptive Server Enterprise (ASE) 11.x through and 12.0 running on HP-UX Sybase ASE consists of an SQL Server and a Backup Server. 1

8 About the Agent About the Agent The following information summarizes the VCS agent processes for SQL Server and Backup Server: SQL Server Agent: Sybase Description Starts a Sybase SQL Server, monitors the SQL Server process, and shuts down a Sybase SQL Server. Operations Online Uses the following command to start the SQL Server: startserver -f $VCS_HOME/install/RUN_$Server Offline Uses the following isql command to stop a SQL Server: shutdown with nowait Monitor Scans process table for dataserver and runs MonScript as an option. Backup Server Agent: SybaseBk Description Starts a Sybase Backup Server, monitors the Backup Server process, and shuts down a Sybase Backup Server. Operations Online Uses the following command to start the Backup Server: startserver -f $VCS_HOME/install/RUN_$BackupServer Offline Uses the following isql command to stop a Backup Server: shutdown with nowait Monitor Scans process table for backupserver. 2 VCS Enterprise Agent for Sybase Installation and Configuration Guide

9 Prerequisites Prerequisites Install and configure VCS. (If necessary, review the VERITAS Cluster Server Installation Guide.) Install and configure the application. (If necessary, review the Sybase documentation.) Verify that the sybase account is a valid and identical Unix account on all systems that will run Sybase. Verify that all systems have enough resources, such as shared memory, to run the Sybase servers. Verify that the Sybase installation directory containing the Sybase binaries and configuration files is located on shared disks. This installation directory is specified by the environment variable $SYBASE. Create the same $SYBASE mount points on each system. Chapter 1, Installing and Configuring the Agent 3

10 Prerequisites Additional Requirements $SYBASE_HOME Directory on Shared Disks All database devices, including master devices, sybsystemprocs, and user, must be located on shared disks. If the database devices are created on file systems, the file systems must also be located on shared disks. Create the same file system mount points on each system. Database Dbspaces If you are using shared disks for dbspaces, change the permissions, or access mode, on the disk groups that store the Sybase data. Change the permissions for sybase to 660. Transparent TCP/IP Failover For transparent failover to Sybase clients, create an IP address as part of the Sybase service group. This IP address must match the dataserver and backup server entries in the $SYBASE_HOME/interfaces file. For information on the format for adding entries to the $SYBASE_HOME/interfaces file, see the Sybase SQL Server documentation. Long Pathname Limitation for $SYBASE_HOME The HP-UX process table limits process pathnames to 63 characters. The full pathname of processes in $SYBASE_HOME can possibly have 64 characters or more. If it does, you can create a soft link to the $SYBASE_HOME directory and use it in place of the long filename in the appropriate Sybase installation files. See Using a Soft Link to a $SYBASE_HOME Pathname on page 16 for a list of files to be edited and examples. 4 VCS Enterprise Agent for Sybase Installation and Configuration Guide

11 Installing the Agent Software Installing the Agent Software 1. Log in as root. 2. Insert the CD into a drive connected to your system. You must mount the CD manually. For example: # mount -F cdfs -o ro /dev/dsk/c0t6d0 /cdrom Where, in this example, /dev/dsk/c0t6d0 is the default for the CD drive. 3. Type the following command to install the agent: # swinstall -s /cdrom VRTSvcssy 4. Repeat steps 1-3 on each system that will become part of the Sybase service group. Chapter 1, Installing and Configuring the Agent 5

12 A Sample Sybase Configuration A Sample Sybase Configuration In the following example, VCS is configured on a two-system cluster (sysa and sysb), and Sybase is installed on shared disks. VCS Private Network System A (sysa) System B (sysb) Shared Disks Public Network Sample Configuration on a Two-System Cluster Configuring the Agent You can configure the Sybase agent using two methods: By using VCS Cluster Manager (the VCS graphical user interface) to edit a resource group template for the Sybase agent. See Configuring the Sybase Agent With Cluster Manager on page 12), or, By using the types configuration files and directly editing the sample main.cf file supplied with the Sybase agent (see Configuring Sybase Agent by Editing the Configuration Files on page 14). This method requires that VCS be stopped and restarted before the configuration takes effect. Before you configure the agent, review the following tables that describe the Sybase resource types and their attributes. The resource type definition files and the sample main.cf configurations are also shown for reference. 6 VCS Enterprise Agent for Sybase Installation and Configuration Guide

13 Configuring the Agent Sybase Resource Type Attributes Type and Dimension Definition Server string-scalar The $DSQUERY Adaptive Server Enterprise (ASE) name. One supported per service group. Owner string-scalar Sybase user as defined owner of executables and database files in /etc/passwd. Home string-scalar $SYBASE path to Sybase binaries and configuration files. Version string-scalar Version of Sybase ASE. SA string-scalar Sybase database administrator. Connects to the ASE for shutdown. SApswd string-scalar Password of Sybase database administrator. Connects to the ASE for shutdown. User (optional) string-scalar Internal database user. Connects to the ASE for secondary monitoring. UPword (optional) string-scalar Password for internal database-user authentication. Db string-scalar Name of the database in which the table resides. Table (optional) string-scalar Name of the table used for secondary monitoring. MonScript (optional) string-scalar Pathname to a secondary monitor script provided for in-depth monitoring; the default (shallow monitoring) is to monitor the database PID only. The pathname to the supplied secondary monitoring script is $VCS_HOME/bin/Sybase/SqlTest.pl. Chapter 1, Installing and Configuring the Agent 7

14 Configuring the Agent Type Definition type Sybase ( str Server str Owner str Version str SA str SApswd str User str UPword str Db str Table str Monscript NameRule = resource.server static str ArgList[] = { Server, Owner, Home, Version, SA, SApswd, User, UPword, Db, Table, Monscript } static str Operations[] = OnOnly ) Sample Configuration Sybase SQL ( Server = SYBASE Owner = "sybase" Home = "/opt/sybase" Version = sybase11 SA = sa SApswd = sybase User = abcd UPword = xxxxxxxx Db = testdb1 Table = testtab Monscript = "/opt/vrtsvcs/bin/sybase/sqltest.pl" ) 8 VCS Enterprise Agent for Sybase Installation and Configuration Guide

15 Configuring the Agent SybaseBk Resource Type Attributes Type and Dimension Definition Server string-scalar The $DSQUERY Backup Server name. Owner string-scalar Sybase user as defined owner of executables and database files in /etc/passwd. Home string-scalar The $SYBASE path to Sybase binaries and configuration files. Version string-scalar Version of Sybase Backup Server. Backupserver string-scalar The $BACKUP Sybase Backup Server name. SA string-scalar Sybase database administrator. Connects to the ASE for shutdown. SApswd string-scalar Password of Sybase database administrator. Connects to the ASE for shutdown. Chapter 1, Installing and Configuring the Agent 9

16 Configuring the Agent Type Definition type SybaseBk ( str Server str Owner str Home str Version str Backupserver str SA str SApswd NameRule = resource.backupserver static str ArgList[] = { Backupserver, Owner, Home, Version, Server, SA, SApswd } ) Sample Configuration Sybase SYBBK ( Server = SYBASE Owner = sybase Home = "/opt/sybase" Version = sybase11 Backupserver= SYB_BACKUP SA = sa SApswd = sybase ) 10 VCS Enterprise Agent for Sybase Installation and Configuration Guide

17 Configuring the Agent Dependencies Among the Sybase and SybaseBk Resources The figure below illustrates the configuration s dependency graph: SybaseBBK SybaseBk SQL sybdatdg_sybprocs sybasesrv IP Sybase opt_sybase Mount sybdatdg_master LVMLogicalVolume LVMLogicalVolume sybase_le0 NIC sybasedg_sybasevol LVMLogicalVolume sybasedg sybdatdg LVMVolumeGroup LVMVolumeGroup This configuration has two volume groups on which three volumes are created. One volume group is for the Sybase home directory and one is for the database. The Mount resource requires the LVMLogicalVolume resource, which in turn requires the LVMVolumeGroup resource type. The service group IP address for the Sybase server is configured using the IP and NIC resource types. The Sybase server can be started after each of these resources is brought online. The Backup Server is started after the SQL Server. Chapter 1, Installing and Configuring the Agent 11

18 Configuring the Sybase Agent With Cluster Manager Configuring the Sybase Agent With Cluster Manager A template for the Sybase resource groups was automatically installed when you installed the Sybase enterprise agent. Using the VCS GUI, you can view the template, which displays the Sybase service group, its resources and their attributes. You can dynamically modify the attributes values as necessary for your configuration. Importing the SybaseTypes.cf File To use the Sybase template, import the SybaseTypes.cf file to the VCS engine by using Cluster Manager: 1. Start Cluster Manager. 2. Click on the File menu and select Import Types. 3. In the Import Types dialog box, select the file: /etc/vrtsvcs/conf/sample_sybase/sybasetypes.cf 4. Import the types file for Sybase. 5. Save the configuration. At this point, the Sybase types have been imported to the VCS engine. The Sybase agent can be configured without interrupting or stopping VCS. For detailed information about using the VCS Cluster Manager, refer to the chapter About the VCS GUI in the VERITAS Cluster Server User s Guide. 12 VCS Enterprise Agent for Sybase Installation and Configuration Guide

19 Configuring the Sybase Agent With Cluster Manager Adding the Sybase Group Using the Wizard If you have imported the SybaseTypes.cf file, you can download the SybaseGroup template by starting the Service Group Configuration Wizard in Cluster Manager. 1. In Cluster Manager, click the service group configuration wizard icon on the toolbar. 2. Click Next on the wizard Welcome window. a. Enter the service group name. In this instance, enter Sybase. b. Select the systems on which the service group will run. 3. Confirm that you are basing the service group on a predefined template: click Next. 4. Select the Sybase template (SybaseGroup) from the list of templates; click Next. 5. The wizard prompts you with alternate names in case the names in the template clash with existing names; make corrections as necessary and click Next. 6. When the wizard indicates that it is ready to create the service group, click Next; the service group is dynamically created based on the Sybase template. 7. Review the service group s resource attributes, and modify the default values, if necessary, in accord with your specific configuration. Caution To create a secure password, see the procedure Setting the Sybase Password Attribute on page 16. Chapter 1, Installing and Configuring the Agent 13

20 Configuring Sybase Agent by Editing the Configuration Files Configuring Sybase Agent by Editing the Configuration Files The VCS enterprise agent for Sybase comes with a sample configuration file that can be used as reference to directly modify your present configuration file. When you use this method, you must restart VCS to implement the configuration. Follow the instructions below to configure the agent using the sample configuration file: 1. Log in to sysa as root. 2. Copy the Sybase types configuration file into place: # cp /etc/vrtsvcs/conf/sample_sybase/sybasetypes.cf /etc/vrtsvcs/conf/config/sybasetypes.cf 3. Make a backup copy of the main.cf file: # cd /etc/vrtsvcs/conf/config # cp main.cf main.cf.orig 4. Edit the main.cf file. The file /etc/vrtsvcs/conf/sample_sybase/main.cf can be used for reference: a. Add an include line for the SybaseTypes.cf file: include "SybaseTypes.cf" b. Create the Sybase and SybaseBk resources. You can refer to the examples shown on page 8 and page 10. c. Edit the default attributes to match the parameters in your configuration. The tables on page 7 and page 9 are provided for reference. Caution From Cluster Manager or hares -display, the Sybase sa password is visible as the attribute value SApswd. As a workaround, SApswd can specify the name of a file that stores the actual password. See Setting the Sybase Password Attribute on page 16. d. Assign dependencies to the newly created resources. Refer to the sample file /etc/vrtsvcs/conf/sample_sybase/main.cf. (See the VCS User s Guide for more information on assigning dependencies.) 5. Save and close the file. 14 VCS Enterprise Agent for Sybase Installation and Configuration Guide

21 Configuring Sybase Agent by Editing the Configuration Files 6. Verify the syntax of the file /etc/vrtsvcs/conf/config/main.cf: # hacf -verify config 7. Start the VCS engine: # hastart 8. Verify that all Sybase service group resources are brought online: # hagrp -display 9. Take the service group offline and verify that all resources are stopped: # hagrp -offline service_group -sys system_name # hagrp -display 10. Bring the service group online again and verify that all resources are available: # hagrp -online service_group -sys system_name # hagrp -display 11. Start the VCS engine on sysb: # hastart 12. Switch the Sybase service group to sysb: # hagrp -switch service_group -to sysb 13. Verify that all Sybase service group resources are brought online on sysb: # hagrp -display Chapter 1, Installing and Configuring the Agent 15

22 Configuring Sybase Agent by Editing the Configuration Files Setting the Sybase Password Attribute From Cluster Manager or hares -display, the Sybase sa password is visible as the attribute value SApswd. As a workaround, SApswd can specify the name of a file that stores the actual password in a single line. The file must have read access for the root user and be present on all nodes where the group can be failed over. 1. To specify a filename for the SApswd attribute from the command line, enter: # hares -modify Sybase SApswd "VCSSY: /sybase/secret" # hares -modify SybaseBk SApswd "VCSSY: /sybase/secret" where /sybase/secret is an example filename, and the keyword VCSSY: (all capitalized letters followed by a colon) must precede the actual name of the file containing the password. Note that the attribute is modified for each resource type, Sybase and SybaseBk. 2. Verify that the file has read access for the root user. 3. Repeat steps 1 and 2 on all systems to which the group can fail over. Using a Soft Link to a $SYBASE_HOME Pathname The HP-UX process table limits process names to 63 characters. A process having a longer pathname is truncated in the table, making it unrecognizable. The Sybase home directory ($SYBASE_HOME) could possibly have such a long pathname. Using a soft link pathname avoids the problems posed by the long pathname. After creating the soft link on each system, you must edit the following files, making the appropriate substitutions: The file RUN_Server in the directory $SYBASE_HOME/install The file RUN_Server_back in the directory $SYBASE_HOME/install The VCS configuration file, /etc/vrtsvcs/conf/config/main.cf 16 VCS Enterprise Agent for Sybase Installation and Configuration Guide

23 Configuring Sybase Agent by Editing the Configuration Files Example, Replacing $SYBASE_HOME Pathname With a Soft Link 1. On each system in the cluster, create a soft link to the long pathname. For example: # ln -s /opt/apps/sybase/home/directory/is/longer/than/ sixty-four/characters/sybase /opt/link_to_longpath Now the process will be invoked with the short pathname of the soft link. 2. In the $SYBASE_HOME/install directory, edit the two files RUN_Server and RUN_Server_back. Find all instances of the long pathname and replace them with the soft link. Replace: /opt/apps/sybase/home/directory/is/longer/than/sixtyfour/characters/sybase with the soft link: /opt/link_to_longpath. For example, the file RUN_Server resembles the following before the change: /opt/apps/sybase/home/directory/is/longer/than/sixty-four /characters/sybase/bin/dataserver\ -sfw17i\ -d/dev/vx/rdsk/db_dg1/vol2\ -e/opt/apps/sybase/home/directory/is/longer /than/sixty-four/characters/sybase/install/fw17i.log\ -M/opt/apps/sybase/home/directory/is/longer/than/sixty-four /characters/sybase\ After the replacement, the file resembles: /opt/link_to_longpath/bin/dataserver\ -sfw17i\ -d/dev/vx/rdsk/db_dg1/vol2\ -e/opt/link_to_longpath/install/fw17i.log\ -M/opt/link_to_longpath\ Note Make sure the -s option and its argument (fw17i in the above example) are the first to be listed; they must be placed within the first 64 characters of the file. 3. In the file /etc/vrtsvcs/conf/config/main.cf, edit the Home attribute for both the Sybase type and the SybaseBk type (refer to Sample Configuration on page 8 and on page 10): For example: Home = "/opt/link_to_longpath" Chapter 1, Installing and Configuring the Agent 17

24 Modifying the Agent Configuration Modifying the Agent Configuration Dynamic Configuration To dynamically configure the VCS enterprise agent for Sybase, see the chapter on reconfiguring VCS from the command line in the VERITAS Cluster Server User s Guide. Database Tables See the comment inside the $VCS_HOME/bin/Sybase/SqlTest.pl script to set up a database table or to become an authenticated user. 18 VCS Enterprise Agent for Sybase Installation and Configuration Guide

25 Modifying the Agent Configuration Additional Monitoring The VCS enterprise agent for Sybase provides two levels of application monitoring: primary and secondary. The primary level monitors the Sybase daemon processes to verify that they are continuously active. The secondary level performs a transaction on a test table in the database to ensure that Sybase is functioning properly. To activate secondary monitoring, the Sybase resource attributes User, Pword, Table, and MonScript must not be empty (""). The attribute MonScript, which points to the $VCS_HOME/bin/Sybase/SQLTest.pl script, must also exist and have execute permission for root. To modify the secondary monitor configuration: 1. Make the VCS configuration writable: # haconf -makerw 2. Set one attribute to an empty string to disable the secondary monitor: # hares -modify Sybase_resource UPword "" 3. We recommend that you freeze the service group to avoid automated actions by VCS caused by incomplete reconfiguration: # hagrp -freeze service_group 4. Update the Sybase database monitor configuration: # /opt/sybase/bin/isql -S "Server" -U "UserName" -P "Password" 5. To enable the secondary monitor, change the UPword attribute to Password: # hares -modify Sybase_resource UPword Password 6. Thaw and save the configuration: # hagrp -unfreeze service_group # haconf -dump [-makero] Chapter 1, Installing and Configuring the Agent 19

26 Disabling the Agent Disabling the Agent To disable the agent, you must first switch the Sybase servers service group to an OFFLINE state. This stops the application completely, or switches the agent to another system. 1. To remove a system from the service group s SystemList, check if the service group is online: # hagrp -state service_group -sys system_name 2. If the service group is online, take it offline by entering one of the following commands: or: # hagrp -switch service_group -to system_name # hagrp -offline service_group -sys system_name 3. Stop the agent on the system by entering: # haagent -stop agent When you get the message Please look for messages in the log file, check the file /var/vrtsvcs/log/engine_a.log for a message confirming the agent has stopped. You can also use the ps command to confirm the agent is stopped. You can now remove the system, service group, or resource type from the VCS configuration. (See the chapter on reconfiguring VCS from the command line in the VERITAS Cluster Server User s Guide.) Removing the Agent Type the following command on each system to remove the agent. Answer prompts accordingly: # swremove VRTSvcssy 20 VCS Enterprise Agent for Sybase Installation and Configuration Guide