19.7 BUILDING A BACKUP SERVER The relationship between the management server (the primary server) and the managed node is extended to other servers that will have responsibility for the node in the event of a primary server failure. The backup server should be installed following the standard OpenView Management server procedure.19.7.1 OpenView Failover Concepts If a failover or takeover becomes necessary it means that the primary server where the node normally sends its messages is no longer available to receive information from its managed nodes. A surrogate server must assume responsibility for the nodes. When the primary server is available, it must resume responsibility for the managed nodes. Therefore, both servers including the primary and all secondary servers must maintain consistent configurations to minimize the time it takes to failover and failback. Configure the management responsibilities (authorization) file called allnodes. Next, install and configure the backup server. Distribution of the all nodes file is final step prior to testing the setup.Download the configuration data. In the GUI, select Action Server Download Configuration .Install the backup server.Distribute the downloaded configuration data to the backup server with the command opcmgrdist .Stop all services on the backup server with ovstop opc .Upload the configuration data to the backup server with the command opccfgupld .Start the services on the backup server with ovstart opc .Distribute the allnodes file and test the backup server. Switch to the backup server using the command on the backup server, opcragt primmgr <node_name> . |