Articles


    The failover acts much the same as a Logscape Manager, it runs the same components that aggregate search results, coordinates monitoring services and visualizes search analytics through a Web Dashboard. The purpose of the Failover is to act as a secondary manager to facilate searches and collate data should your main manager go offline.


    Note: While pre-3.0 Installations can include a failover, there is no official support for pre-3.0 failovers.


    Duration: Just under 5 minutes

    Prerequisites: Make sure that you have Oracle Java 7 and above and that Java is accessible from your path, as well as a pre-configured Logscape environment.

    1. Download the latest version of Logscape

    2. Navigate to your Logscape installation and inside the scripts folder, type:

    3. A prompt will appear to configure your installation. Choose option 5) for a Failover

    4. Next you will be asked for the address/hostname of your Manager. A quick test is executed to check the connectivity between your host and the Manager.

    5. Once the test has completed you can accept the default configuration for the other parameters by pressing enter.

      7. Navigate back to the Logscape home directory and type the command below to start the Failover Manager.

      logscape $> ./logscape.sh start

    7. Browse Getting Started

    Deploying the connection.properties file

    In order to make use of a failover agent your environment must contain a connection.properties file. This file is relatively simple and can be uploaded via the deployment page from your management agent.

    • Note the IP and port that your manager and failover instances are running on
    • Create the connection.properties file
    • Add the following options to the connection.properties file
      • manager.address="stcp://IP:PORT"
      • failover.address="stcp://IP:PORT"
    • Once deployed and every agent has downloaded a copy your failover is ready.