Configuring for Replication/Disaster Recovery for Milestone XProtect
    • 25 Apr 2024
    • PDF

    Configuring for Replication/Disaster Recovery for Milestone XProtect

    • PDF

    Article Summary

    Activating the Disaster Recovery (DR) functionality using WSC is easy. This functionality can be activated on your Recording storage(s), your Archive(s), or both.

    Activating Disaster Recovery

    1. Start the Milestone XProtect Management Client application.
    2. In the WSC section of the navigation menu, click Disaster Recovery.
    3. Click Enable, as shown below.

    4. Configure your cloud target by entering the following.
      If Storage Extension has already been configured, you will NOT be prompted for cloud details as your data will NOT be replicated twice. The same dataset is used.

      Server URL — Set this to the appropriate region service URL.
      Access Key — This is auto-populated.
      Secret Key — This is auto-populated. 

      Click List buckets and select the bucket you want to use as the target for the recordings.

      Make sure you select a DIFFERENT bucket/container for EACH volume.

      Click OK when you are done.

    5. To start the replication process, switch Inactive to Active (top right).

    Within a few minutes (depending how many cameras and files are managed), WSC software will start replicating and display the percentage of local data that has been replicated to the cloud. After all existing files have been replicated, this number will typically be just shy of 100%, unless you stop the camera streams or the recording server in order for the most current data to reach your Wasabi target.

    Verifying Your Internet is Keeping Up

    Open Task Manager on the Recording Server to see how fast WSC can upload to the cloud. Click the Performance tab, and then select Ethernet. Unless other processes are running in the background, the Receive will show the incoming camera data while the Send shows the rate at which WSC is uploading to the cloud. On average, the Send should be no less than the Receive:

    The example on the left shows a problematic situation where Send bandwidth is less than Receive. This means WSC is currently not able to keep up with the incoming data flow. WSC is barely keeping up on the right and 25% headroom would be desirable (showing about 12%). The percentage of uploaded camera data should continue to increase and eventually stabilize around 99%.