Consider the following items before starting the implementation:
You must include the Sybase environment variables in your shell start-up script (for example, the /bin/tcsh start-up script finds its environment variables in the .tcshrc file). Make sure that you can start and stop Adaptive Server from the shell before adding IRIX FailSafe to the Adaptive Server start-up procedures.
The Adaptive Server installations may reside on local or shared file systems. If they reside on a shared file system, they cannot have the same absolute path. For example, Adaptive Server may be installed in /node1_Sybase on the primary node and on /node2_Sybase on the secondary node.
Sybase recommends that each node contain its own copy of Adaptive Server. If synchronization of information is required, use the command rsync to perform the synchronization. For more information about rsync, see your SGI documentation.
Use logical volumes even when they comprise one disk; if there is disk contention, this allows you to add more drives without affecting the Adaptive Server administration.
Do not allocate a disk drive to more than one Adaptive
Server.
The master device for each installation must reside on shared logical volumes or shared file systems.
Adaptive Server devices must reside on the shared disks. Determine which raw logical volumes or file system files will be used for Adaptive Server devices. You must determine whether Adaptive Server uses file system files or raw logical volumes. Raw logical volumes give better performance than file systems.
Use symbolic links to map raw device names to local
file names when you issue the disk init...physname parameter.
If the logical volume name changes, stop Adaptive Server, change
the volumes, re-create the symbolic link, and restart Adaptive Server.
The System Administrator assigns the names for both the primary and secondary companions.
The primary and secondary Adaptive Server companions must have enough resources configured to allow for successful failover. During planning, consider resources such as memory, user logins, and so on.
| Copyright © 2005. Sybase Inc. All rights reserved. |
|
|
