Storage Foundation for Sybase ASE CE 7.4.1 Configuration and Upgrade Guide - Linux

Last Published:
Product(s): InfoScale & Storage Foundation (7.4.1)
Platform: Linux
  1. Section I. Configuring SF Sybase ASE CE
    1. Preparing to configure SF Sybase CE
      1.  
        About this document
      2.  
        Supported Sybase ASE CE releases
      3.  
        Supported SF Sybase CE configurations
      4.  
        Coordinator disk requirements for I/O fencing
      5.  
        Supported replication technologies for global clusters
      6. About planning to configure I/O fencing
        1.  
          Typical SF Sybase CE cluster configuration with disk-based I/O fencing
      7.  
        Planning for cluster management
    2. Configuring SF Sybase CE
      1.  
        About configuring SF Sybase CE
      2. Configuring the SF Sybase CE components using the script-based installer
        1. Configuring the SF Sybase CE cluster
          1.  
            Configuring the cluster name
          2.  
            Configuring private heartbeat links
          3.  
            Configuring the virtual IP of the cluster
          4. Configuring SF Sybase CE in secure mode
            1.  
              Setting up trust relationships for your SF Sybase CE cluster
          5. Configuring a secure cluster node by node
            1.  
              Configuring the first node
            2.  
              Configuring the remaining nodes
            3.  
              Completing the secure cluster configuration
          6.  
            Adding VCS users
          7.  
            Configuring SMTP email notification
          8.  
            Configuring SNMP trap notification
          9.  
            Configuring global clusters
    3. Configuring SF Sybase CE clusters for data integrity
      1. Setting up disk-based I/O fencing using installer
        1.  
          Initializing disks as VxVM disks
        2.  
          Identifying disks to use as coordinator disks
        3.  
          Refreshing keys or registrations on the existing coordination points for disk-based fencing using the installer
        4. Checking shared disks for I/O fencing
          1.  
            Verifying Array Support Library (ASL)
          2.  
            Verifying that the nodes have access to the same disk
          3.  
            Testing the disks using vxfentsthdw utility
        5.  
          Configuring disk-based I/O fencing using installer
    4. Performing an automated SF Sybase CE configuration
      1.  
        Configuring SF Sybase CE using response files
      2.  
        Response file variables to configure SF Sybase CE
      3.  
        Sample response files for configuring SF Sybase CE
    5. Performing an automated I/O fencing configuration using response files
      1.  
        Configuring I/O fencing using response files
      2.  
        Response file variables to configure disk-based I/O fencing
      3.  
        Sample response file for configuring disk-based I/O fencing
    6. Configuring a cluster under VCS control using a response file
      1.  
        Configuring a Sybase cluster under VCS control with a response file
      2.  
        Response file variables to configure SF Sybase CE in VCS
  2. Section II. Post-installation and configuration tasks
    1. Verifying the installation
      1.  
        Upgrading the disk group version
      2.  
        Performing a postcheck on a node
      3.  
        Verifying SF Sybase CE installation using VCS configuration file
      4. Verifying LLT, GAB, and cluster operation
        1.  
          Verifying LLT
        2.  
          Verifying GAB
        3.  
          Verifying the cluster
        4.  
          Verifying the cluster nodes
    2. Performing additional post-installation and configuration tasks
      1. About enabling LDAP authentication for clusters that run in secure mode
        1.  
          Enabling LDAP authentication for clusters that run in secure mode
      2.  
        Configuring Volume Replicator
      3.  
        Running SORT Data Collector to collect configuration information
  3. Section III. Upgrade of SF Sybase CE
    1. Planning to upgrade SF Sybase CE
      1.  
        About the upgrade
      2.  
        Supported upgrade paths
      3.  
        Using Install Bundles to simultaneously install or upgrade full releases (base, maintenance, rolling patch), and individual patches
    2. Performing a full upgrade of SF Sybase CE using the product installer
      1.  
        About full upgrades
      2.  
        Preparing to perform a full upgrade to SF Sybase CE 7.4.1
      3. Upgrading to SF Sybase CE 7.4.1
        1.  
          Upgrading SF Sybase CE using the Veritas installation program
    3. Performing an automated full upgrade of SF Sybase CE using response files
      1.  
        Upgrading SF Sybase CE using a response file
      2.  
        Response file variables to upgrade SF Sybase CE
      3.  
        Sample response file for upgrading SF Sybase CE
    4. Performing a phased upgrade of SF Sybase CE
      1.  
        About phased upgrade
      2. Performing a phased upgrade of SF Sybase CE from version 6.2.1 and later release
        1.  
          Step 1: Performing pre-upgrade tasks on the first half of the cluster
        2.  
          Step 2: Upgrading the first half of the cluster
        3.  
          Step 3: Performing pre-upgrade tasks on the second half of the cluster
        4.  
          Step 4: Performing post-upgrade tasks on the first half of the cluster
        5.  
          Step 5: Upgrading the second half of the cluster
        6.  
          Step 6: Performing post-upgrade tasks on the second half of the cluster
    5. Performing a rolling upgrade of SF Sybase CE
      1.  
        About rolling upgrade
      2.  
        Supported rolling upgrade paths
      3.  
        Preparing to perform a rolling upgrade to SF Sybase CE 7.4.1
    6. Performing post-upgrade tasks
      1.  
        Re-joining the backup boot disk group into the current disk group
      2.  
        Reverting to the backup boot disk group after an unsuccessful upgrade
      3.  
        Setting or changing the product license level
      4.  
        Upgrading disk layout versions
      5.  
        Upgrading CVM protocol version and VxVM disk group version
  4. Section IV. Installation and upgrade of Sybase ASE CE
    1. Installing, configuring, and upgrading Sybase ASE CE
      1.  
        Before installing Sybase ASE CE
      2.  
        Preparing for local mount point on VxFS for Sybase ASE CE binary installation
      3.  
        Preparing for shared mount point on CFS for Sybase ASE CE binary installation
      4.  
        Installing Sybase ASE CE software
      5.  
        Preparing to create a Sybase ASE CE cluster
      6.  
        Creating the Sybase ASE CE cluster
      7. Preparing to configure the Sybase instances under VCS control
        1.  
          Language settings for the Sybase agent
        2.  
          Configuring Sybase for detail monitoring
        3.  
          Encrypting passwords for Sybase
        4. About setting up detail monitoring for the agent for Sybase
          1.  
            Enabling detail monitoring for the agent for Sybase
          2.  
            Disabling detail monitoring for the agent for Sybase
      8.  
        Configuring a Sybase ASE CE cluster under VCS control using the SF Sybase CE installer
      9.  
        Upgrading Sybase ASE CE
  5. Section V. Adding and removing nodes
    1. Adding a node to SF Sybase CE clusters
      1.  
        About adding a node to a cluster
      2.  
        Before adding a node to a cluster
      3. Adding the node to a cluster manually
        1.  
          Starting Veritas Volume Manager (VxVM) on the new node
        2.  
          Configuring cluster processes on the new node
        3. Setting up the node to run in secure mode
          1.  
            Configuring the authentication broker on node sys5
        4.  
          Starting fencing on the new node
        5.  
          Configuring Cluster Volume Manager (CVM) and Cluster File System (CFS) on the new node
        6.  
          After adding the new node
        7.  
          Configuring the ClusterService group for the new node
      4.  
        Adding a node to a cluster using the Veritas InfoScale installer
      5. Adding the new instance to the Sybase ASE CE cluster
        1.  
          Creating Sybase user and groups
        2.  
          Preparing the mount point for Sybase resources on the new node
        3.  
          Adding a new Sybase ASE CE instance to the Sybase ASE CE cluster
        4.  
          Bringing the new Sybase ASE CE instance under VCS control
    2. Removing a node from SF Sybase CE clusters
      1.  
        About removing a node from a cluster
      2.  
        Removing a node from a cluster
      3.  
        Modifying the VCS configuration files on existing nodes
      4.  
        Modifying the Cluster Volume Manager (CVM) configuration on the existing nodes to remove references to the deleted node
      5.  
        Removing security credentials from the leaving node
  6. Section VI. Configuration of disaster recovery environments
    1. Configuring disaster recovery environments
      1.  
        Disaster recovery options for SF Sybase CE
      2.  
        About setting up a global cluster environment for SF Sybase CE
      3.  
        About configuring a parallel global cluster using Volume Replicator (VVR) for replication
  7. Section VII. Installation reference
    1. Appendix A. Installation scripts
      1.  
        Installation script options
      2.  
        About using the postcheck option
    2. Appendix B. Sample installation and configuration values
      1.  
        SF Sybase CE installation and configuration information
      2.  
        SF Sybase CE worksheet
    3. Appendix C. Tunable files for installation
      1.  
        About setting tunable parameters using the installer or a response file
      2.  
        Setting tunables for an installation, configuration, or upgrade
      3.  
        Setting tunables with no other installer-related operations
      4.  
        Setting tunables with an un-integrated response file
      5.  
        Preparing the tunables file
      6.  
        Setting parameters for the tunables file
      7.  
        Tunables value parameter definitions
    4. Appendix D. Configuration files
      1.  
        About sample main.cf files
      2. Sample main.cf files for Sybase ASE CE configurations
        1.  
          Sample main.cf for a basic Sybase ASE CE cluster configuration under VCS control with shared mount point on CFS for Sybase binary installation
        2.  
          Sample main.cf for a basic Sybase ASE CE cluster configuration with local mount point on VxFS for Sybase binary installation
        3.  
          Sample main.cf for a primary CVM VVR site
        4.  
          Sample main.cf for a secondary CVM VVR site
    5. Appendix E. Configuring the secure shell or the remote shell for communications
      1. About configuring secure shell or remote shell communication modes before installing products
        1.  
          Manually configuring passwordless ssh
        2.  
          Setting up ssh and rsh connection using the installer -comsetup command
        3.  
          Setting up ssh and rsh connection using the pwdutil.pl utility
        4.  
          Restarting the ssh session
        5.  
          Enabling rsh for Linux
    6. Appendix F. High availability agent information
      1. About agents
        1.  
          VCS agents included within SF Sybase CE
        2.  
          VCS agent for Sybase included within SF Sybase CE
      2. CVMCluster agent
        1.  
          Entry points for CVMCluster agent
        2.  
          Attribute definition for CVMCluster agent
        3.  
          CVMCluster agent type definition
        4.  
          CVMCluster agent sample configuration
      3. CVMVxconfigd agent
        1.  
          Entry points for CVMVxconfigd agent
        2.  
          Attribute definition for CVMVxconfigd agent
        3.  
          CVMVxconfigd agent type definition
        4.  
          CVMVxconfigd agent sample configuration
      4. CVMVolDg agent
        1.  
          Entry points for CVMVolDg agent
        2.  
          Attribute definition for CVMVolDg agent
        3.  
          CVMVolDg agent type definition
        4.  
          CVMVolDg agent sample configuration
      5. CFSMount agent
        1.  
          Entry points for CFSMount agent
        2.  
          Attribute definition for CFSMount agent
        3.  
          CFSMount agent type definition
        4.  
          CFSMount agent sample configuration
      6. Process agent
        1.  
          Agent functions
        2.  
          State definitions
        3.  
          Attributes
        4.  
          Resource type definition
        5.  
          Sample configurations
      7.  
        Monitoring options for the Sybase agent
      8. Sybase resource type
        1.  
          Type definition for the Sybase agent
        2.  
          Attribute definitions for the Sybase agent

Attribute definitions for the Sybase agent

Review the description of the Sybase agent attributes. The agent attributes are classified as required, optional, and internal.

Table: Required attributes lists the required attributes.

Table: Required attributes

Required Attributes

Definition

Home

The $SYBASE path to Sybase binaries and configuration files.

Type and dimension: string-scalar

Default value: No default value

Owner

Sybase user as the defined owner of executables and database files in any of the sources (such as NIS+, /etc/hosts, and so on) specified in the /etc/nsswitch.conf file for passwd entry. The Sybase executables and database files are accessed in the context of this user.

Type and dimension: string-scalar

Quorum_dev

The quorum device manages the cluster membership, stores cluster configuration data, and contains information shared among server instances and nodes. The quorum device is a disk that is accessible to all the nodes in the cluster. Specify a fully qualified quorum device name.

Type and dimension: string-scalar

Default value: No default value

Note: This attribute should be specified only for the cluster edition.

Note:

If you do not set the Quorum_dev attribute for Sybase Cluster Edition, the Sybase agent does not perform the qrmutil-based checks. This error in configuration may lead to undesirable results. For example, if qrmutil returns failure pending, the agent does not panic the system.

SA

Sybase database administrator. This attribute is required to connect to the ASE for shutdown.

Type and dimension: string-scalar

Default value: No default value

SApswd

Encrypted password for Sybase database administrator. This password is required to connect to the ASE for shutdown.

Type and dimension: string-scalar

Default value: No default value

Note:

You need not specify a value for this attribute if the SA user does not require a password.

Server

The $DSQUERY ASE name. Only one server should be configured in a Sybase service group. The advantage of configuring Sybase resources in a separate service group is, each Sybase data server can failover independently.

Type and dimension: string-scalar

Default value: No default value

Version

Version of Sybase ASE.

Type and dimension: string-scalar

Default value: No default value

Note:

After the Sybase resource is online in VCS, you must not modify the Home and Version attributes. For the Sybase cluster edition, setting invalid values for Home and Version attributes when the resource is in Online state causes the node to panic.

Note:

For Sybase cluster edition, after the Sybase resource is online in VCS, you must not modify the Home and Version attributes. For the Sybase cluster edition, setting invalid values for Home and Version attributes when the resource is in Online state causes the node to panic.

Table: Optional attributes lists the optional attributes.

Table: Optional attributes

Optional Attributes

Definition

DetailMonitor

Specifies whether the Sybase server is monitored in detail. A positive integer value indicates that the resource monitors the Sybase server in detail. Value 0 denotes it does not.

Note:

This attribute has been removed from the agent version 6.1.0 onwwards.

Default is 0.

Type and dimension: int-scalar

Note:

The DetailMonitor attribute is deprecated in SF Sybase CE 7.4.1. Instead, LevelTwoMonitorFreq attribute at the Sybase resource type level may be used.

LevelTwoMonitorFreq

Specifies the frequency at which the agent for this resource type must perform second-level or detailed monitoring.

This is a resource type level attribute. You can override the value of this attribute at the resource level.

The default value of LevelTwoMonitorFreq attribute is 0 (zero).

If required, the value of LevelTwoMonitorFreq attribute can be overridden at resource level.

User

The database user, in the context of which, the transactions are performed on the database. You must specify a value for this attribute if LevelTwoMonitorFreq is set to a positive integer value.

Type and dimension: string-scalar

Default value: No default value

UPword

Encrypted password for the database user. You must specify a value for this attribute if LevelTwoMonitorFreq is set to a positive integer value. However, you need not specify a value for this attribute if the database user does not require a password.

intercType and dimension: string-scalar

Default value: No default value

Db

Name of the database used for detailed monitoring. The table used by the detail monitor script resides in this database. You must specify a value for this attribute if LevelTwoMonitorFreq is set to a positive integer value.

Type and dimension: string-scalar

Default value: No default value

Table

Name of the table on which the detail monitoring script performs the transactions. You must specify a value for this attribute if LevelTwoMonitorFreq is set to a positive integer value.

Type and dimension: string-scalar

Default value: No default value

Monscript

The path to the detail monitor script; the default value for this attribute is the path for the script, SqlTest.pl, provided with the agent. You must specify a value for this attribute if LevelTwoMonitorFreq is set to a positive integer value.

Type and dimension: string-scalar

Default value: No default value

Note:

By default, SqlTest.pl script has the execute permission set. If you specify custom detail monitor script, ensure that custom detail monitor script also has the execute permissions set.

Run_ServerFile

Specifies the location of the RUN_SERVER file for the Sybase instance. The default location of this file is used if no value is specified for this attribute.

Type and dimension: string-scalar

Default value: No default value

IMF

This resource-type level attribute determines whether the Sybase agent must perform intelligent resource monitoring. You can also override the value of this attribute at resource-level.

This attribute includes the following keys:

  • Mode: Define this attribute to enable or disable intelligent resource monitoring.

    Valid values are as follows:

    • 0 - Does not perform intelligent resource monitoring

    • 1 - Performs intelligent resource monitoring for offline resources and performs poll-based monitoring for online resources

    • 2 - Performs intelligent resource monitoring for online resources and performs poll-based monitoring for offline resources

    • 3 - Performs intelligent resource monitoring for both online and for offline resources

      Default: 3

IMF (cont.)

  • MonitorFreq: This key value specifies the frequency at which the agent invokes the monitor agent function. The value of this key is an integer.

    Default: 5

    You can set this key to a non-zero value for cases where the agent requires to perform both poll-based and intelligent resource monitoring. If the value is 0, the agent does not perform poll-based process check monitoring.

    After the resource registers with the AMF kernel driver, the agent calls the monitor agent function as follows:

    • After every (MonitorFreq x MonitorInterval) number of seconds for online resources

    • After every (MonitorFreq x OfflineMonitorInterval) number of seconds for offline resources

  • RegisterRetryLimit: If you enable intelligent resource monitoring, the agent invokes the sybase_imf_register agent function to register the resource with the AMFkernel driver. The value of the RegisterRetryLimit key determines the number of times the agent must retry registration for a resource. If the agent cannot register the resource within the limit that is specified, then intelligent monitoring is disabled until the resource state changes or the value of the Mode key changes.

    Default: 3

Type and dimension: Integer-association.

interfaces_File

Specifies the location of interfaces file, including the directory name and the file name for the Sybase instance. If this attribute is configured, [-I interfaces file] option is used when connecting to the isql session. If this attribute is not configured, the agent does not use the -I option.

Type and dimension: string-scalar

Default value: No default value

For example: /sybase/my_interfaces_file

Note:

It is assumed that you have modified the RUN_ServerFile with the non-default interface file location if the interfaces_File attribute is configured.

DelayAfterOnline

Specifies the number of seconds that elapse after the Online entry point is complete and before the next monitor cycle is invoked.

Type and dimension: integer-scalar

Default value: 10

DelayAfterOffline

Specifies the number of seconds that elapse after the Offline entry point is complete and before the next monitor cycle is invoked.

Type and dimension: integer-scalar

Default value: 2

ShutdownWaitLimit

Maximum number of seconds for which the agent waits for the Sybase instance to stop after issuing the shutdown with wait command, and before attempting to issue the kill -15 <data server-pid> command, if required.

Type and dimension: integer-scalar

Default value: 60

Quorum_dev

The quorum device manages the cluster membership, stores cluster configuration data and contains information shared among server instances and nodes. It must be a disk accessible to all nodes in the cluster. Specify fully qualified quorum device name.

Note:

If you do not set the Quorum_dev attribute for Sybase Cluster Edition, the Sybase agent does not perform the qrmutil-based checks. This error in configuration may lead to undesirable results. For example, if qrmutil returns failure pending, the agent does not panic the system.

Type and dimension: String-scalar

Default value: No default value

Run_ServerFile

Specifies the location of the RUN_SERVER file of the Sybase instance. The default location of the file is used if no value is specified for this attribute.

Type and dimension: String-scalar

Default value: No default value

More Information

Encrypting passwords for Sybase

Encrypting passwords for Sybase