How do I use Salient CompleteView VMS with Wasabi Surveillance Cloud?

Salient Systems CompleteView VMS is validated for use with Wasabi Surveillance Cloud. Salient Systems' CompleteView is an open-platform video management solution. 

Prerequisites

Pre Configuration

1. If you don't have an access and secret key pair (API Keys), you can create one by following the instructions here.

Note - For activation and installation of Wasabi Surveillance Cloud software instructions, please refer to this Knowledge Base article.

Configuration

1. Wasabi Surveillance Cloud should be installed on the same server on which CompleteView recording server is installed on. If multiple recording servers are deployed, install the WSC software on each server. The same credentials can be used across all servers. 

2. Now, launch the WSC app to begin configuration. 

3. Select the folder you defined in CompleteView as a Volume by clicking the “Add Source” button. If more than one Volume has been configured in CompleteView, add each folder separately. Do not add sub-folders whose parent folder has been added as a source.

mceclip0.png

4. Click on the down arrow next to Targets and select the existing 'Wasabi' profile, to auto fill the access and secret keys. You can optionally enter the keys manually.

mceclip0.png

5. Select the appropriate region in which you want to store the video recordings.

6. Click on Create Bucket to create a new bucket in your WSC account. Use the bucket naming conventions specified here. Click OK when done.

mceclip1.png

6. Click Apply to apply the configuration changes.

At this point, the Surveillance Cloud software is setup to begin replicating all the data in the source folder to the Wasabi bucket. After all configurations steps have been performed, click the “Resume” button (first click on Wasabi Surveillance Cloud at the top left) to start the service. Replication of data to the cloud will commence immediately.

mceclip2.png

You can login to the Wasabi console and confirm if the data is being written to the bucket with the same directory structure as seen on the local storage.

Additional Configuration Information

Disaster Recovery Policy
Mirror Copies the customer data to the cloud. Both data sets are identical (the one on-prem, and one in the cloud) Bridge makes a full copy of local data to the cloud for redundancy.

Storage Extension Settings
In this case, Instead of a mirror copy, you're simply extending the capability of local storage to the cloud. The older data is in the cloud, while the newest data sits locally. After X number of days, the data is deleted from the local drive to free up on-prem capacity, but data is still in the cloud if/when it needs to be accessed.

Disaster Recovery + Storage Extension
By combining both options, as soon as the data lands on disk, it replicates to the cloud. Data is only deleted from the local drive when it hits the retention (perhaps 7th day, whatever the customer requires), then it's off the local drive but you can still retrieve it instantly from the cloud

Have more questions? Submit a request