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

Tunables value parameter definitions

When you create a tunables file for the installer you can only use the parameters in the following list.

Prior to making any updates to the tunables, refer to the Storage Foundation Cluster File System High Availability Administrator's Guide for detailed information on product tunable ranges and recommendations.

Table: Supported tunable parameters describes the supported tunable parameters that can be specified in a tunables file.

Table: Supported tunable parameters

Tunable

Description

autoreminor

(Veritas Volume Manager) Enable reminoring in case of conflicts during disk group import.

autostartvolumes

(Veritas Volume Manager) Enable the automatic recovery of volumes.

dmp_cache_open

(Dynamic Multi-Pathing) Whether the first open on a device performed by an array support library (ASL) is cached.

dmp_daemon_count

(Dynamic Multi-Pathing) The number of kernel threads for DMP administrative tasks.

dmp_delayq_interval

(Dynamic Multi-Pathing) The time interval for which DMP delays the error processing if the device is busy.

dmp_fast_recovery

(Dynamic Multi-Pathing) Whether DMP should attempt to obtain SCSI error information directly from the HBA interface. This tunable must be set after Dynamic Multi-Pathing is started.

dmp_health_time

(Dynamic Multi-Pathing) The time in seconds for which a path must stay healthy.

dmp_log_level

(Dynamic Multi-Pathing) The level of detail to which DMP console messages are displayed.

dmp_low_impact_probe

(Dynamic Multi-Pathing) Whether the low impact path probing feature is enabled.

dmp_lun_retry_timeout

(Dynamic Multi-Pathing) The retry period for handling transient errors.

dmp_monitor_fabric

(Dynamic Multi-Pathing) Whether the Event Source daemon (vxesd) uses the Storage Networking Industry Association (SNIA) HBA API. This tunable must be set after Dynamic Multi-Pathing is started.

dmp_monitor_ownership

(Dynamic Multi-Pathing) Whether the dynamic change in LUN ownership is monitored.

dmp_native_support

(Dynamic Multi-Pathing) Whether DMP does multi-pathing for native devices.

dmp_path_age

(Dynamic Multi-Pathing) The time for which an intermittently failing path needs to be monitored before DMP marks it as healthy.

dmp_pathswitch_blks_shift

(Dynamic Multi-Pathing) The default number of contiguous I/O blocks sent along a DMP path to an array before switching to the next available path.

dmp_probe_idle_lun

(Dynamic Multi-Pathing) Whether the path restoration kernel thread probes idle LUNs.

dmp_probe_threshold

(Dynamic Multi-Pathing) The number of paths will be probed by the restore daemon.

dmp_restore_cycles

(Dynamic Multi-Pathing) The number of cycles between running the check_all policy when the restore policy is check_periodic.

dmp_restore_interval

(Dynamic Multi-Pathing) The time interval in seconds the restore daemon analyzes the condition of paths.

dmp_restore_policy

(Dynamic Multi-Pathing) The policy used by DMP path restoration thread.

dmp_restore_state

(Dynamic Multi-Pathing) Whether kernel thread for DMP path restoration is started.

dmp_retry_count

(Dynamic Multi-Pathing) The number of times a path reports a path busy error consecutively before DMP marks the path as failed.

dmp_scsi_timeout

(Dynamic Multi-Pathing) The timeout value for any SCSI command sent via DMP.

dmp_sfg_threshold

(Dynamic Multi-Pathing) The status of the subpaths failover group (SFG) feature.

dmp_stat_interval

(Dynamic Multi-Pathing) The time interval between gathering DMP statistics.

fssmartmovethreshold

(Veritas Volume Manager) The file system usage threshold for SmartMove (percent). This tunable must be set after Veritas Volume Manager is started.

max_diskq

(Veritas File System) Specifies the maximum disk queue generated by a single file. The installer can only set the system default value of max_diskq. Refer to the tunefstab(4) manual page for setting this tunable for a specified block device.

read_ahead

(Veritas File System) The 0 value disables read ahead functionality, the 1 value (default) retains traditional sequential read ahead behavior, and the 2 value enables enhanced read ahead for all reads. The installer can only set the system default value of read_ahead. Refer to the tunefstab(4) manual page for setting this tunable for a specified block device.

read_nstream

(Veritas File System) The number of parallel read requests of size read_pref_io that can be outstanding at one time. The installer can only set the system default value of read_nstream. Refer to the tunefstab(4) manual page for setting this tunable for a specified block device.

read_pref_io

(Veritas File System) The preferred read request size. The installer can only set the system default value of read_pref_io. Refer to the tunefstab(4) manual page for setting this tunable for a specified block device.

reclaim_on_delete_start_time

(Veritas Volume Manager) Time of day to start reclamation for deleted volumes. This tunable must be set after Veritas Volume Manager is started.

reclaim_on_delete_wait_period

(Veritas Volume Manager) Days to wait before starting reclamation for deleted volumes. This tunable must be set after Veritas Volume Manager is started.

same_key_for_alldgs

(Veritas Volume Manager) Use the same fencing key for all disk groups. This tunable must be set after Veritas Volume Manager is started.

sharedminorstart

(Veritas Volume Manager) Start of range to use for minor numbers for shared disk groups. This tunable must be set after Veritas Volume Manager is started.

storage_connectivity

(Veritas Volume Manager) The CVM storage connectivity type. This tunable must be set after Veritas Volume Manager is started.

usefssmartmove

(Veritas Volume Manager) Configure SmartMove feature (all, thinonly, none). This tunable must be set after Veritas Volume Manager is started.

vol_checkpt_default

(Veritas File System) Size of VxVM storage checkpoints (kBytes). This tunable requires a system reboot to take effect.

vol_cmpres_enabled

(Veritas Volume Manager) Allow enabling compression for Volume Replicator.

vol_cmpres_threads

(Veritas Volume Manager) Maximum number of compression threads for Volume Replicator.

vol_default_iodelay

(Veritas Volume Manager) Time to pause between I/O requests from VxVM utilities (10ms units). This tunable requires a system reboot to take effect.

vol_fmr_logsz

(Veritas Volume Manager) Maximum size of bitmap Fast Mirror Resync uses to track changed blocks (KBytes). This tunable requires a system reboot to take effect.

vol_max_adminio_poolsz

(Veritas Volume Manager) Maximum amount of memory used by VxVM admin I/O's (bytes). This tunable requires a system reboot to take effect.

vol_max_nmpool_sz

(Veritas Volume Manager) Maximum name pool size (bytes).

vol_max_rdback_sz

(Veritas Volume Manager) Storage Record readback pool maximum (bytes).

vol_max_wrspool_sz

(Veritas Volume Manager) Maximum memory used in clustered version of Volume Replicator .

vol_maxio

(Veritas Volume Manager) Maximum size of logical VxVM I/O operations (kBytes). This tunable requires a system reboot to take effect.

vol_maxioctl

(Veritas Volume Manager) Maximum size of data passed into the VxVM ioctl calls (bytes). This tunable requires a system reboot to take effect.

vol_maxparallelio

(Veritas Volume Manager) Number of I/O operations vxconfigd can request at one time. This tunable requires a system reboot to take effect.

vol_maxspecialio

(Veritas Volume Manager) Maximum size of a VxVM I/O operation issued by an ioctl call (kBytes). This tunable requires a system reboot to take effect.

vol_min_lowmem_sz

(Veritas Volume Manager) Low water mark for memory (bytes).

vol_nm_hb_timeout

(Veritas Volume Manager) Volume Replicator timeout value (ticks).

vol_rvio_maxpool_sz

(Veritas Volume Manager) Maximum memory requested by Volume Replicator (bytes).

vol_stats_enable

(Veritas Volume Manager) Enable VxVM I/O stat collection.

vol_subdisk_num

(Veritas Volume Manager) Maximum number of subdisks attached to a single VxVM plex. This tunable requires a system reboot to take effect.

voldrl_max_drtregs

(Veritas Volume Manager) Maximum number of dirty VxVM regions. This tunable requires a system reboot to take effect.

voldrl_max_seq_dirty

(Veritas Volume Manager) Maximum number of dirty regions in sequential mode. This tunable requires a system reboot to take effect.

voldrl_min_regionsz

(Veritas Volume Manager) Minimum size of a VxVM Dirty Region Logging (DRL) region (kBytes). This tunable requires a system reboot to take effect.

voldrl_volumemax_drtregs

(Veritas Volume Manager) Max per volume dirty regions in log-plex DRL.

voldrl_volumemax_drtregs_20

(Veritas Volume Manager) Max per volume dirty regions in DCO version 20.

voldrl_dirty_regions

(Veritas Volume Manager) Number of regions cached for DCO version 30.

voliomem_chunk_size

(Veritas Volume Manager) Size of VxVM memory allocation requests (bytes). This tunable requires a system reboot to take effect.

voliomem_maxpool_sz

(Veritas Volume Manager) Maximum amount of memory used by VxVM (bytes). This tunable requires a system reboot to take effect.

voliot_errbuf_dflt

(Veritas Volume Manager) Size of a VxVM error trace buffer (bytes). This tunable requires a system reboot to take effect.

voliot_iobuf_default

(Veritas Volume Manager) Default size of a VxVM I/O trace buffer (bytes). This tunable requires a system reboot to take effect.

voliot_iobuf_limit

(Veritas Volume Manager) Maximum total size of all VxVM I/O trace buffers (bytes). This tunable requires a system reboot to take effect.

voliot_iobuf_max

(Veritas Volume Manager) Maximum size of a VxVM I/O trace buffer (bytes). This tunable requires a system reboot to take effect.

voliot_max_open

(Veritas Volume Manager) Maximum number of VxVM trace channels available for vxtrace commands. This tunable requires a system reboot to take effect.

volpagemod_max_memsz

(Veritas Volume Manager) Maximum paging module memory used by Instant Snapshots (Kbytes).

volraid_rsrtransmax

(Veritas Volume Manager) Maximum number of VxVM RAID-5 transient reconstruct operations in parallel. This tunable requires a system reboot to take effect.

vxfs_mbuf

(Veritas File System) Maximum memory used for VxFS buffer cache. This tunable requires a system reboot to take effect.

vxfs_ninode

(Veritas File System) Number of entries in the VxFS inode table. This tunable requires a system reboot to take effect.

write_nstream

(Veritas File System) The number of parallel write requests of size write_pref_io that can be outstanding at one time. The installer can only set the system default value of write_nstream. Refer to the tunefstab(4) manual page for setting this tunable for a specified block device.

write_pref_io

(Veritas File System) The preferred write request size. The installer can only set the system default value of write_pref_io. Refer to the tunefstab(4) manual page for setting this tunable for a specified block device.