How do I use Senstar Symphony with Wasabi?

Senstar Symphony Common Operating Platform is certified for use with Wasabi. The Senstar Symphony™ Common Operating Platform is a modular solution for security management and data intelligence. For more information, please refer to our joint solution brief available here.



1. Create a bucket in your Wasabi account. Create a bucket per recording server. Do not use a shared bucket for multiple servers.

2. Install, configure and activate your Senstar Symphony product.

3. Install and activate Tiger Surveillance Bridge

4. Select the Senstar - Symphony VMS Profile on Surveillance Bridge.

5. In the Tiger Surveillance Bridge application select archive to be backed up / moved to Wasabi Cloud storage using the Add Source button.


6. Next, in the pop up window select Wasabi and hit OK. Enter the Wasabi Access key and Secret key information and then click “List Buckets” and select the bucket to use. Click Apply when done.



Note - In the example above, we are using the US-East-1 region service URL. You should enter the service URL of the region where your bucket is located in. You will find the different Wasabi region service URLs on this Knowledge Base article

At this point, the Bridge 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 to start the service. Replication of data to the cloud will commence immediately.

Note - No configuration is needed in Senstar Symphony product to use Tiger Surveillance Bridge and Wasabi Hot Cloud storage.

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 Options supported on the Surveillance Bridge app and validated with Wasabi:-

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