Documente Academic
Documente Profesional
Documente Cultură
N11191F
January 2004
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.
Chapter 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Supported Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
About the VCS Enterprise Agent for Sybase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
SQL Server Agent: Sybase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Backup Server Agent: SybaseBk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Monitoring Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
How the Agent makes Sybase Highly Available . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Typical Sybase Configuration in a VCS Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Setting Up a Sybase Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
iii
Language Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39
Contents v
vi VCS Enterprise Agent for Sybase Installation and Configuration Guide
Preface
This book describes how to install and configure the VERITAS Cluster ServerTM (VCS)
Enterprise Agent 4.0 for Sybase.
If this document is dated more than six months prior to the date you are installing your
enterprise agent, contact VERITAS Technical Support to confirm you have the latest
supported versions of the application and operating systems.
vii
Getting Help
Getting Help
For technical assistance, visit the VERITAS Technical Services Web site at
http://support.veritas.com. From there you can:
Contact the VERITAS Technical Services staff and post questions to them.
Download the latest patches and utilities.
View the VERITAS Cluster Server Frequently Asked Questions (FAQ) page.
Search the knowledge base for answers to technical support questions.
Receive automatic notice of product updates.
Learn about VERITAS Cluster Server training.
Read white papers related to VERITAS Cluster Server.
Access the latest product documentation and technical notes.
Conventions
Typeface/Font Usage
italic new terms, book titles, emphasis, variables in tables or body text
Symbol Usage
viii VCS Enterprise Agent for Sybase Installation and Configuration Guide
Introduction 1
VERITAS Cluster ServerTM (VCS) enterprise agents monitor specific resources within an
enterprise application, determine the status of these resources, and start or stop them
according to external events. The VCS enterprise agent for Sybase provides high
availability for Sybase in a VCS Cluster.
VCS Enterprise Agent for Sybase provides active/passive support for Sybase. For
active/active support, contact Sybase for their agent.
Supported Software
Sybase Adaptive Server Enterprise (ASE) 11.x through 11.9.2, 12.0, and 12.5. ASE
consists of a SQL Server and a Backup Server.
Solaris 2.6, 2.7, 2.8, and 2.9.
VCS 4.0.
1
About the VCS Enterprise Agent for Sybase
Chapter 1, Introduction 3
Monitoring Options
Monitoring Options
The VCS enterprise agent for Sybase provides two levels of application monitoring:
primary (basic) and secondary (detail).
The basic level monitors the Sybase daemon processes to verify that they are running.
Detail monitoring performs a transaction on a test table in the database to ensure that
Sybase is functioning properly. See Setting Up Detail Monitoring for Sybase Agent on
page 24 for more information about modifying monitoring options for a Sybase agent.
Node 1 Node 2
Sybase
Binaries &
Data
Public Network
Chapter 1, Introduction 5
Typical Sybase Configuration in a VCS Cluster
In the configuration depicted in the illustration below, the Sybase binaries are installed
locally on each node in the cluster and the Sybase data is on shared disks or shared cluster
disk groups managed using VxVM.
Node 1 Node 2
Sybase
Data
Public Network
Chapter 1, Introduction 7
Setting Up a Sybase Cluster
Prerequisites
Install and configure VCS. If necessary, see the VERITAS Cluster Server Installation
Guide.
Verify that all systems in the cluster have adequate resources to run Sybase and VCS.
9
Additional Considerations for Installing Sybase
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.
For example, if you are using VERITAS Volume Manager, type:
# vxedit -g diskgroup_name set group=dba
user=sybase mode=660 volume_name
Language Settings
For the Sybase Enterprise Agent to function with the desired locale, make sure that the
Sybase installation has the correct localization files. For example, if the Sybase server
requires LANG=en_US.UTF-8 environment variable, verify that the localization files
corresponding to language en_US.UTF-8 are installed with Sybase. Also, edit the file
$VCS_HOME/bin/vcsenv to contain the following:
LANG=en_US.UTF-8;export LANG
The above change would affect all VCS agents.
Prerequisites
Install and configure VCS. VERITAS recommends installing the VCS graphical user
interface. 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 valid and identical on all UNIX systems that will
run Sybase.
If a previous version of the agent is installed, uninstall it.
13
Installation Instructions
Installation Instructions
1. Log in as root.
If you are not running Solaris volume-management software, you must mount
the CD manually. For example:
# mount -F hsfs -o ro /dev/dsk/c0t6d0s2 /mnt
Where, in this example, /dev/dsk/c0t6d0s2 is the default for the CD drive.
# cd /mnt
# pkgadd -d .
Note Repeat steps 1 and 2 on each system that will become part of the Sybase service
group.
2. Follow step a through step c on all systems that have the Sybase agent installed.
c. Install the VCS enterprise agent 4.0 for Sybase. See Installation Instructions on
page 14.
Prerequisites
Install and configure Sybase identically on all cluster systems. (For more information,
see Installing Sybase on page 9)
Verify that the Sybase agent is installed on all cluster systems. (For more information,
see Installing the Sybase Agent on page 13)
17
Configuring the Agent Using Cluster Manager (Java Console)
1. In Cluster Manager, click the service group configuration wizard icon on the toolbar.
3. Confirm that you are basing the service group on a predefined template, and click
Next.
4. Select the Sybase template (SybaseGroup) from the list of templates, and 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 groups resource attributes, and modify the default values, if
necessary, in accord with your specific configuration.
Caution To create a secure password, see Setting the Sybase Password Attribute on
page 22.
b. Create the Sybase and SybaseBk resources. Refer to the examples shown under
Sybase Resource Type on page 31 and SybaseBk Resource Type on page 33.
Caution From hagui or hares -display, the Sybase sa password is visible as the
attribute value SApswd. For added security, use SApswd to specify the name of
a file that stores the actual password. See Setting the Sybase Password
Attribute on page 22.
d. Assign dependencies to the newly created resources. Refer to the sample file
/etc/VRTSvcs/conf/sample_sybase/main.cf. (See the VERITAS Cluster
Server Users Guide for more information on assigning dependencies.)
8. Verify that all Sybase service group resources are brought online:
# hagrp -state
9. Take the service group offline and verify that all resources are stopped:
# hagrp -offline service_group -sys system_name
# hagrp -state
10. Bring the service group online again and verify that all resources are available:
# hagrp -online service_group -sys system_name
# hagrp -state
13. Verify that all Sybase service group resources are brought online on sysb:
# hagrp -state
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. 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.
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
eighty/characters/sybase /opt/link_to_longpath
Now the process will be invoked with the short pathname of the soft link.
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 eighty characters of the file.
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.
3. Freeze the service group to avoid automated actions by VCS caused by incomplete
reconfiguration:
# hagrp -freeze service_group
# /opt/Sybase/bin/isql -S "Server"
-U "UserName" -P "Password"
Note The location of the executable isql varies by Sybase version. For Sybase 11.x, the
path is $SYBASE/bin. For Sybase 12.0, the path is $SYBASE/$SBYASE_OCS/bin.
2. Right-click the service group name, and select Enable Resources. This enables all the
resources in the group.
3. Right-click the service group name, and select the systems on which to enable the
service group (Right-click>Enable>system_name or Right-click>Enable>All).
5. Right-click the service group and select to online the service group on the system
(Right-click>Online>system_name).
2. Choose Offline, and choose the appropriate system from the pop-up menu
(Right-click>Offline>system_name).
27
Switching the Service Group
1. On the Service Groups tab of Cluster Explorer configuration tree, right-click the
service group.
or
Select the cluster in the Cluster Explorer configuration tree, select the Service Groups
tab, and right-click the service group icon in the view panel.
2. Choose Switch To, and choose the appropriate system from the pop-up menu
(Right-click>Switch To>system_name).
31
Sybase Resource Type
Attribute Definitions
Server string-scalar The $DSQUERY ASE name. One supported per service
group.
Attribute Definitions
35
Resource Dependency Graph
SYBBK
SybaseBk
SQL
Sybase
sybasesrv
opt_Sybase
IP Volume Volume
Mount sybdatdg_master
sybdatdg_sybprocs
sybasedg_sybasevol
This configuration has two disk groups on which three volumes are created. One disk
group is for the Sybase server, and one is for the database. The mount resource requires
the Volume resource, which in turn requires the DiskGroup resource. 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.
Note If your configuration does not use VERITAS Volume Manager, use the
DiskReservation resource type to configure shared storage instead of DiskGroup
and Volume resource types.
Sample Configuration
include "types.cf"
include "SybaseTypes.cf"
cluster vcs (
)
system sysa
system sysb
group sybase (
SystemList = { sysa, sysb }
AutoStart = 1
AutoStartList = { sysa }
)
DiskGroup sybasedg (
DiskGroup = sybasedg
)
DiskGroup sybdatdg (
DiskGroup = sybdatdg
)
IP sybasesrv (
Device = le0
Address = "16.9.1.9"
)
Mount opt_Sybase (
MountPoint = "/opt/Sybase"
BlockDevice = "/dev/vx/dsk/sybasedg/ase1103"
FsckOpt = "-n"
FSType = vxfs
MountOpt = rw
)
NIC sybase_le0 (
Device = le0
NetworkType = ether
)
Sybase SQL (
Server = SYBASE
Owner = sybase
Home = "/opt/Sybase"
Version = sybase11
SA = sa
SApswd = sybase
User = abcd
UPword = xxxxxxx
Db = testdb1
Table = testtab
Monscript = "/opt/VRTSvcs/bin/Sybase/SqlTest.pl"
)
SybaseBk SYBBK (
Server = SYBASE
Owner = sybase
Home = "/opt/Sybase"
Version = sybase11
Backupserver = SYB_BACKUP
SA = sa
SApswd = sybase
)
Volume sybasedg_sybasevol (
Volume = ase1103
DiskGroup = sybasedg
)
Volume sybdatdg_master (
Volume = master_1103
DiskGroup = sybdatdg
)
Volume sybdatdg_sybprocs (
Volume = sysprocs_1103
DiskGroup = sybdatdg
)
39
Monscript 32 configuration in a cluster 5
Owner 32 database dbspaces 10
SA 32 directory on shared disks 10
SApswd 32 installation 10
Server 32 language settings 11
Table 32 long pathname limitations 10
UPword 32 password attribute 22
User 32 transparent TCP/IP failover 10
Version 32
W
Supported software 1
wizard 19
Switching service groups 28
Sybase