This section includes the following topics:
Installing the Precise product suite in a failover application tends to be more complex than installing in a regular application. It is highly recommended that you consult with Precise Customer Support prior to such an installation.
In a live standby (or active/passive) configuration, an application runs on a primary server, or node. A dedicated secondary, or "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.
The datafiles, IP addresses, and other resources of the application may be active on only one node at a time. When the software detects that a resource has failed, it relocates the failed resource to the standby server.
Two of these resources affect the Precise installation:
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.
When preparing a UNIX server, verify that a dedicated Precise UNIX user is created on both physical servers, with the correct Oracle UNIX user group. Preferably, both UNIX users should have the same password.
Post-installation tasks are mandatory.
To prepare servers for Precise 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 only
cd precise installation directory
infra\bin\psin_listener_java.exe -o install
infra\bin\psin_sentry.exe -o install
Installing the SQL Server Tier Collector in active/passive configurations requires post-installation tasks.
To perform post-installation tasks for SQL Server
products\sql-server\install\pssq_install
products\sql-server
folder.products\sql-server\install\pssq_symmetrix_install
SYMMETRIX
.Installing the Sybase Tier Collector in active/passive configurations requires post-installation tasks.
To perform post-installation tasks for Sybase
products\sybase\install\pssy_install
products\sybase
folder.Installing the Microsoft .NET Tier Collector in active/passive configurations requires post-installation tasks.
To perform post-installation tasks for Microsoft .NET
products\dotnet\install\psdn_col_service_install.bat
command.products\dotnot\install\psdn_injector.exe
command.regsvr32 /s products\dotnot\bin\i4np.dll
command.products\dotnet\install\psdn_gac_all.bat
command.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 Network
<Precise_root>/products/insight
folder.<Precise_root>/products/insight/host
folder and run the following command:echo "<Precise_root>"|products\insight\install\i3_general.exe -install
<Precise_root>
and the | character.\products\insight\host\install
reinstall_network_cards.bat
script.network_rot.sh
script from the following folder: .\products\insight\host\install
<Precise_root>\products\i3fp\registry\products\insight\hosts\logical server name.xml
<ips>
section and change the IP address to the IP of the physical server.infra\bin\psin_cli.bat -action update-main-registry -i3-user <user>
-i3-clear-password <password> -registry-path
/registry/products/insight/hosts/<server>
./infra/bin/psin_cli.sh -action update-main-registry -i3-
user <user>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 agents
<Precise_root>/products/insight
folder.<Precise_root>\products\i3fp\registry\instances\tuxedo\logical server name\instance name.xml
file.<instance_name>
, add the line: <tux_shmkey>0xXXXXXX</tux_shmkey>
infra\bin\psin_cli.bat -action update-main-registry -i3-user <user>
-i3-clear-password <password> -registry-path
/registry/instances/tuxedo/<server>/<instance>
./infra/bin/psin_cli.sh -action update-main-registry -i3-user <user>
-i3-clear-password <password> -registry-path
/registry/instances/tuxedo/<server>/<instance>
<Precise_root>/products/insight/host
folder and run the following command:echo<Precise_root> "<precise_root>"|..\install\i3_general.exe -install
<precise_root>
and the | character.Installing Oracle Tier agents in active/passive configurations requires the following preconditions:
Pre-installation and installation tasks are not required, but post-installation tasks are mandatory if the Insight Savvy for Oracle is installed.
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 agents
<Precise_root>/products/insight/host
folder and run the following command:echo "<Precise_root>"|...\install\i3_general.exe -install
<Precise_root>
and the | character.When the monitored application fails over to the standby server, all Precise agents must fail over, too. It is recommended that you add Precise shutdown and startup scripts to your automatic failover procedure.
See Generating Precise startup and shutdown scripts on page 212.
AdminPoint shows the status for Precise agents that run on the active server. Precise agents on the standby server are not represented. |
The following figure illustrates the live standby configuration before a failover.
Figure 1 Live standby configuration before a failover
The following figure illustrates the live standby configuration after a failover.
Figure 2 Live standby configuration after a failover
If you added the Precise shutdown and startup scripts to your automatic failover procedure, you do not need to perform any tasks when a failover occurs. Otherwise, you need to perform the following task.
To perform failover tasks in active/passive configurations
Start all Precise agents on the now active server.
Upon failover, you must stop all services before starting them on the active server. Verify that you stop the sentry service first. |
In a parallel partitions cluster (such as Oracle RAC/OPS), an application can run concurrently on more than one server. The different instances either do not share anything or are designed for parallel access of shared resources.
As with other cluster configurations, clients connect to the application by a logical name, and load balancing software or hardware distributes the workload to the multiple servers.
In this configuration, Precise refers to each server - and each instance on this server - by its physical name. That is, each server is defined as a Precise server machine, and each monitored instance on each server is defined separately in Precise Agent Installer.
Figure 3 Parallel partitions configuration in an Oracle application
To install Precise components in parallel partitions configurations, you first have to prepare the involved servers. Before you prepare the servers, verify that you can connect from the Precise FocalPoint server to the physical server by using its physical name and IP address.
To prepare servers for Precise in active/active configurations, in Precise Installer, in the New Server dialog box, use the physical server name.
Before installing Oracle Tier agents in parallel partitions configurations, verify that you can perform SQL connect from the physical server and from the PMDB FocalPoint server to each database node by using the physical name and the node name.
You can add Precise startup and shutdown scripts to your automatic failover procedure by running a command:
cd <Precise installation folder>
infra\bin\psin_infra.exe -handle-agents (stop|start)
cd <Precise installation folder>
nohup ./infra/bin/psin_infra -handle-agents (stop|start) &
When installing Precise for SQL Server in a cluster application, you can choose between the following cluster configurations:
Precise for SQL Server as a standalone application
In this configuration, Precise for SQL Server is installed locally on each node of the cluster. In a failover situation, the data gathered will not be available.
Only the Precise Collector on the active node will sample the instance. Other nodes will remain in recovery mode, until failover occurs. |
Precise for SQL Server on remote servers (using the virtual instance name of the cluster)
Precise for SQL Server is installed on a third server and sampling through the network. The product is not aware that this is a cluster application.
In a failover situation, the data gathered will be available.
This configuration is only suitable for the cluster active/passive configuration. |
The following procedures explain how to set up Precise for SQL Server as part of a cluster (option 1). In this option, you need to configure the following Precise services in Microsoft Cluster Manager so that they start automatically whenever a failover situation occurs:
Verify that you have already installed these services on each of the nodes in the cluster. See Installing live standby configurations (active/passive) on page 205.
To add the Precise for SQL Server Collector service
Precise for SQL Server Collector <instance name>
PssMSSql{instance-name}80 <Listener_unique_ID>
To add the Precise SQL Server Storage Collector service (only if Precise for Storage is installed)
Precise SQL Server Storage Collector <instance name>
PssMSSqlStorage{instance name}80 <Listener_unique_ID>
To add the Precise Listener service
Precise Listener
psin_listener_v8.7