Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


Disaster Recovery in JSA Deployments


Implement Disaster Recovery (DR) to safeguard your JSA configurations and data by mirroring your data to another identical JSA system. Disaster recovery is possible when you have two identical JSA systems in separate geographic environments that are a mirror of each other, and data is collected at both sites.

Enable disaster recovery (DR) when you forward live data, for example, flows and events from a primary JSA system, to a parallel system at another site. Forwarding data uses off-site forwarding, which is set up on both the primary and secondary deployments. You can set up disaster recovery with deployments that are in different geographical locations.

Choose one of the following disaster recovery deployment scenarios:

  • Primary JSA console and backup console--A hardware failure solution, where the backup console is a copy of the primary server, with the same configuration. Only one console is operational at any one time. If the primary console fails, you manually switch to the backup console, apply the primary configuration backup, and use the IP address from the primary console. After you restore the primary server and before you turn it on, you manually turn off the backup server. If the system is down for a long time, apply the backup console configuration backup to the primary server.

  • Event and flow forwarding--Events and flows are forwarded from a primary site to a secondary site. Identical architectures in two separate data centers are required.

  • Distributing the same events and flows to the primary and secondary sites-- Distribute the same event and flow data to two live sites by using a load balancer or other method to deliver the same data to mirrored appliances. Each site has a record of the log data that is sent.