Set up Disaster Recovery (Site-to-site VPN)

You can set up disaster recovery using your Site-to-site VPN connection between two Yeastar P-Series Software Editions, so as to ensure the continuous availability of essential telephony services in the event of a disaster.

Requirements

Both servers in a disaster recovery pair must meet the following requirements.

Item Requirement
Product Model Yeastar P-Series Software Edition
Plan Ultimate Plan
Version Same firmware version and must be 83.12.0.57 or later.
Network LAN port as the default Ethernet interface and a static IP address is required.
External Storage Identical storage device settings and mounting points.

Prerequisites

You have connected two Yeastar P-Series Software Editions using Site-to-site VPN, and they can communicate with each other.

Procedure

To implement disaster recovery, you need to complete the following settings on both Working Server and Redundancy Server.

  1. Log in to PBX web portal, go to System > High Availability > Disaster Recovery.
  2. Enable disaster recovery and set the remote networking method.

    1. On the top of the page, turn on the Enable Disaster Recovery switch.
    2. In the Remote Networking Method drop-down list, select Site-to-site VPN.
  3. Complete the following settings for the disaster recovery pair.
    Working Server
    Setting Description
    Server Mode Select Working Server.
    Note: If you have set up Hot Standby, only the Primary Server can act as Working Server.
    Working Server Host Name

    Enter a name to help you identify the Working Server when receiving event notifications.

    Note: The Working Server Host Name set in the Working Server and Redundancy Server should be the same to avoid confusion in event notifications.
    Redundancy Server Host Name

    Enter a name to help you identify the Redundancy Server when receiving event notifications.

    Note: The Redundancy Server Host Name set in the Working Server and Redundancy Server should be the same to avoid confusion in event notifications.
    Network Connection Detection

    Enter a network detection node (e.g. the gateway address of VPN router) to detect the Working Server's connection to the VPN.

    This helps prevent an unexpected takeover if the Redundancy Server doesn't receive heartbeat response from the Working Server.
    Access Code Set an access code.
    Note: The two PBXs must have the same access code to authenticate connection.
    Redundancy Server IP Address Enter the IP address assigned to the Redundancy Server in your VPN network.
    Redundancy Server
    Setting Description
    Server Information
    Server Mode Select Redundancy Server.
    Working Server Host Name

    Enter a name to help you identify the Working Server when receiving event notifications.

    Note: The Working Server Host Name set in the Working Server and Redundancy Server should be the same to avoid confusion in event notifications.
    Redundancy Server Host Name

    Enter a name to help you identify the Redundancy Server when receiving event notifications.

    Note: The Redundancy Server Host Name set in the Working Server and Redundancy Server should be the same to avoid confusion in event notifications.
    Network Connection Detection

    Enter a network detection node to detect the Redundancy Server's connection to the VPN.

    This helps prevent an unexpected takeover if the Redundancy Server doesn't receive heartbeat response.
    Access Code Set an access code.
    Note: The two PBXs must have the same access code to authenticate connection.
    Working Server IP Address
    Enter the IP address based on the deployment environment of the Working Server.
    • If Hot Standby is enabled, enter the virtual IP.
    • If Hot Standby is disabled, enter the IP address assigned to the Working Server in your VPN network.
    Advanced
    Heartbeat Interval (s) Define the frequency to send heartbeat packets.

    The default value is 2 seconds, which means that the Redundancy Server sends packets every 2 seconds to detect whether the Working Server is alive or not.
    Dead Time (s) Define the maximum time interval before the Working Server responds to the Redundancy Server.
    The default value is 150 seconds. If the Redundancy Server receives no response after timeout, it will take over the telephony services automatically.
    Note: If you have set up Hot Standby, the value set here MUST be greater than the Dead Time in Hot Standby, with a minimum difference of 30 seconds.
  4. Click Save.

    The system prompts that you need to reboot the PBXs to make disaster recovery take effect.

  5. Click Reboot Now.

Result

After rebooting the PBXs, you can check the disaster recovery status on PBX web portal:
  • On Working Server, the status is displayed as Working, indicating that the server is running to provide all PBX functions.

  • On Redundancy Server, the status is displayed as In Redundancy, indicating that the server is in redundancy status. The Redundancy Server will now replicate data from the Working Server.

What to do next

Read Server Redundancy on SIP Trunks and WebRTC Trunks and Server Redundancy on SIP Devices and Linkus UC Clients to learn how server redundancy can be implemented on trunks and extension endpoints.