Page History

...

In a live standby (or active/passive) configuration, an application runs on a primary server, or node. A dedicated secondary, or “backup"backup,” " server exists to take over if the primary server fails. The backup server is passive, meaning that it is not performing any other function.

...

Two of these resources affect the Precise installation:

• File

...

• system. Both servers must have access to at least one shared file system. This file system can be either (a) accessible from all servers at all times, or (b) accessible only from active node. In case of (b), all post-installation tasks described later must be postponed until the shared file system is accessible from the standby node.
• IP addresses and host

...

• names. Clients must know the application by a logical name, which is relocated - with the application - to the active server. Otherwise, all clients will have to be updated on each server failover.
  This logical name transparency can be achieved as follows:

  ...

  • • The active server is dynamically configured on each failover with the cluster IP address. This is also called Virtual IP Address.

  ...

  • • An intermediate hardware or software unit that gets client IP packets and routes them to the active servers. In this case, the logical cluster name, which is the cluster IP address and host name, is hidden from the physical server in the cluster.

  Preparing servers for Precise in active/passive configurations

  To install Precise components in active/passive configurations, you first have to prepare the involved servers. As a prerequisite, the Precise installation must reside on a shared file system and be accessible from the active server.

  ...

  To prepare servers for Precise in active/passive configurations1.    In

  1. In the Precise Installer, in the New Server dialog box, use the logical server name only. Do not use the physical server name anywhere.

  ...

  1. For a UNIX server, verify that a Precise installation folder is specified on a shared file system, such as /shared/i3.

  ...

  1. Add the logical server once, regardless of the physical server at the time of installation.

  Post-preparation tasks for servers in active/passive configurations

  You need to perform additional tasks after you prepared the servers in Precise Agent Installer.

  Edit the <precise_root>/infra/host/hostname.txt file and add the names of all servers in the configuration as new lines. For example:
       SUN5_physical1
       SUN5_physical2
       SUN5_virtual

  To perform post-preparation tasks on Windows only1.    Log

  1. Log in to the active server and open the Services window.

  ...

  1. Change the Startup type of all Precise services to Manual.

  ...

  1. Activate the passive server; then log in to it and run the following commands to create the Precise Listener service:
     cd precise installation directory
infra\bin\psin_listener_java.exe -o install
infra\bin\psin_sentry.exe -o install

  Post-installation tasks for the SQL Server Tier Collector in active/passive configurations

  Installing the SQL Server Tier Collector in active/passive configurations requires post-installation tasks.

  To perform post-installation tasks for SQL Server1.    Run

  1. Run the following command:
     products\sql-server\install\pssq_install

  ...

  1. Press Enter and then type the value of the instance name as it appears in the products\sql-server folder.

  ...

  1. If Precise for Storage is installed for an SQL Server database:

     ...

     1. 1. Run the following command:
           products\sql-server\install\pssq_symmetrix_install

     ...

     1. 1. Press Enter and then type SYMMETRIX.

     ...

     1. Change the Startup type of each created service to Manual.

     Post-installation tasks for the Sybase Tier Collector in active/passive configurations

     Installing the Sybase Tier Collector in active/passive configurations requires post-installation tasks.

     To perform post-installation tasks for Sybase1.    Run

     1. Run the following command:
        products\sybase\install\pssy_install

     ...

     1. Press Enter and then type the value of the instance name as it appears in the products\sybase folder.

     ...

     1. Change the Startup type of each created service to Manual.

     Post-installation tasks for the Microsoft .NET Tier Collector in active/passive configurations

     Installing the Microsoft .NET Tier Collector in active/passive configurations requires post-installation tasks.

     To perform post-installation tasks for Microsoft .NET1.    Install

     1. Install at least one .NET instance on the active server via the Precise Installer.

     ...

     1. On the passive server, perform the following actions:

        ...

        1. 1. Run the products\dotnet\install\psdn_col_service_install.bat command.

        ...

        1. 1. Run the products\

        ...

        1. 1. dotnot\install\psdn_injector.exe command.

        ...

        1. 1. Run the regsvr32 /s products\

        ...

        1. 1. dotnot\bin\i4np.dll command.

        ...

        1. 1. Run the products\dotnet\install\psdn_gac_all.bat command.

        ...

        1. After performing these steps, you can continue to install more .NET instances on either server.

        Post-installation tasks for Insight Savvies for OS and Network in active/passive configurations

        Installing the Insight Savvies for OS and Network in active/passive configurations requires post-installation tasks.

        To perform post-installation tasks for Insight Savvies for OS and Network1.    Log

        1. Log in to the passive server.

        ...

        1. Change to the

        ...

        1. <Precise_

        ...

        1. root>/products/insight folder.

        ...

        1. On Windows only, change to the

        ...

        1. <Precise_

        ...

        1. root>/products/insight/host folder and run the following command:
           echo "

        ...

        1. <Precise_

        ...

        1. root>"|products\insight\install\i3_general.exe -install
           Do not type blanks

        ...

        1. between <Precise_root> and the | character.

        ...

        1. Only if Insight Savvy for Network is installed:

           ...

           1. 1. Install the network driver on the passive physical server, as follows:
                 Windows

              ...

              1. 1. 1. Log in to the passive server.

              ...

              1. 1. 1. Change to the following folder:
                       \products\insight\host\install

              ...

              1. 1. 1. Run the reinstall_network_cards.bat script.
                    UNIX

                 ...

                 1. 1. 1. Log in to the passive server as root user.

                 ...

                 1. 1. 1. Run the network_

                 ...

                 1. 1. 1. rot.sh script from the following folder: .\products\insight\host\install

                 ...

                 1. Only if Insight Savvy for Network is installed:

                    ...

                    1. 1. Include the IP address of the physical servers in the FocalPoint registry file on the server where Precise FocalPoint is installed, as follows:

                       ...

                       1. 1. 1. Open the following file:
                                

                       ...

                       1. 1. 1. <Precise_

                       ...

                       1. 1. 1. root>\products\i3fp\registry\products\insight\hosts\logical server name.xml

                       ...

                       1. 1. 1. Copy the existing physical server section to the <ips> section and change the IP address to the IP of the physical server.
                                For example, for a cluster whose active server IP address is 10.1.1.1 and whose passive server IP address is 10.1.1.2, this section would look as follows:
                                     <ips>
                                     <child_1>
                                          <ip>10.1.1.1</ip>
                                     </child_1>
                                     <child_2>
                                          <ip>10.1.1.2</ip>
                                     </child_2>
                                     </ips>

                       ...

                       1. 1. 1. Sync the registry changes by running the following command on the FocalPoint where you've updated the registry files:
                                • Windows
                                  infra\bin\psin_cli.bat -action update-main-registry -i3-user <user

                       ...

                       1. 1. 1. • >
-i3-clear-password

                       ...

                       1. 1. 1. • <password> -registry-path
/registry/products/insight/hosts/

                       ...

                       1. 1. 1. • <server>
                                • UNIX
                                  ./infra/bin/psin_cli.sh -action update-main-registry -i3-user <user

                       ...

                       1. 1. 1. • >
                                  -i3-clear-password <password

                       ...

                       1. 1. 1. • > -registry-path
                                  /registry/products/insight/hosts/

                       ...

                       1. 1. 1. • <server>

                       Post-installation tasks for Tuxedo Tier agents in active/passive configurations

                       Installing Tuxedo Tier agents in active/passive configurations requires manual post-installation tasks.

                       When trying to find the Tuxedo shared memory address to attach during initialization, the Insight Savvy for Tuxedo uses the physical server name. If the logical server name is used during the installation, this may cause connection issues. To prevent connection issues, you need to configure the shared memory address in the registry file by adding the <tux_shmkey> parameter. This parameter takes on the hexadecimal value of the shared memory address as defined in the Tuxedo configuration file. For example:

                            *RESOURCES
                             IPCKEY 100100

                       In this example, 100100 is the decimal string for the hexadecimal value 0x18704. The following is a complete Tuxedo configuration example from the Precise registry:

                            <simple>
                                 <tux_dir>/vip/Tuxedo71/sun4</tux_dir>
                                 <tux_version>71</tux_version>
                                 <tux_config>/vip/Tuxedo71/sun4/samples/atmi/simpapp/
                                 tuxconfig</tux_config>
                                 <tux_uid>7101</tux_uid>
                                 <tux_shmkey>0x18704</tux_shmkey>
                                 <network>
                                      <ports>
                                           <child_1>
                                                <port>0</port>
                                           </child_1>
                                      </ports>
                                 </network>
                            </simple>

                       To perform post-installation tasks for Tuxedo Tier agents1.    Log

                       1. Log in to the passive server and change to the 

                       ...

                       1. <Precise_

                       ...

                       1. root>/products/insight folder.

                       ...

                       1. Configure the shared memory address in the registry file to prevent connection issues, as follows:

                          ...

                          1. 1. To prevent connection issues, configure the shared memory address in the registry file, as follows:

                             ...

                             1. 1. 1. Open the <Precise_root>\products\i3fp\registry\instances\tuxedo\logical server name\instance name.xml file.

                             ...

                             1. 1. 1. Under <instance_name>, add the line:
                                      <tux_shmkey>0xXXXXXX</tux_shmkey>

                             ...

                             1. 1. 1. Sync the registry changes by running the following command on the FocalPoint where you've updated the registry files:

                             ...

                             1. 1. 1. • Windows
                                        

                             ...

                             1. 1. 1. • infra

                             ...

                             1. 1. 1. • \bin

                             ...

                             1. 1. 1. • \psin_cli.

                             ...

                             1. 1. 1. • bat -action update-main-registry -i3-user

                             ...

                             1. 1. 1. • <user>
-i3-clear-password <password

                             ...

                             1. 1. 1. • > -registry-path
/registry/instances/tuxedo/

                             ...

                             Windows

                             ...

                             1. 1. 1. • <server>/<instance>
                                      • UNIX
                                        ./infra/bin/psin_cli.

                             ...

                             1. 1. 1. • sh -action update-main-registry -i3-user <user>
-i3-clear-password <password> -registry-path
/registry/instances/tuxedo/<server>/<instance>

                             ...

                             1. 1. On Windows only, change to the

                             ...

                             1. 1. <Precise_

                             ...

                             1. 1. root>/products/insight/host folder and run the following command:
                                   

                             ...

                             1. 1. echo<Precise_root> "<precise_root>"|..\install\i3_general.exe -install
                                   Do not type blanks between

                             ...

                             1. 1. <precise_root

                             ...

                             1. 1. > and the | character.

                             Installing the Oracle Tier agents in active/passive configurations

                             Installing Oracle Tier agents in active/passive configurations requires the following preconditions:•    The

                             • The monitored Oracle database is installed on both servers with the same instance ID.

                             ...

                             • Both databases share the same Oracle data via a shared file system and shared disks.

                             ...

                             • Oracle instances and servers are accessible using the logical name of the cluster.

                             ...

                             • Because only one database is active at a time, the Precise for Oracle agents monitor only the active instance at any given moment.

                             Pre-installation and installation tasks are not required, but post-installation tasks are mandatory if the Insight Savvy for Oracle is installed.

                             Post-installation tasks for Oracle Tier agents in active/passive configurations

                             If you have installed the Insight Savvy for Oracle, you need to perform manual post-installation tasks.

                             To perform post-installation tasks for Oracle Tier agents1.    Log

                             1. Log in to the passive server and change to the <precise_root>/products/insight folder.

                             ...

                             1. On Windows only, change to the  <precise_root>/products/insight/host folder and run the following command:

                             echo "<precise_root>"|..\install\i3_general.exe -install

                             ...

                             Precise Website	Solutions	Support	Support Portal	Community	About Us	Legal