How do I use VIVOTEK VAST 2 with Wasabi?

VIVOTEK VAST 2 is validated for use with Wasabi. VIVOTEK’s VAST 2 is an IP video management software used in video surveillance and analytics use cases.


Reference Architecture Diagram



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 Vivotek VAST 2 product.

Note - Configure the VAST2 total retention period to cover local storage + cloud. 


3. Install and activate Tiger Surveillance Bridge

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


5. Navigate to the storage repository you want to configure


6. Choose the Wasabi option as shown below -


7. Enter your Wasabi account access key and secret access key, hit List buckets, select your bucket (make sure to create a different bucket for each recording server), and then hit Apply.

Note - In the example below, 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


8. On the Settings page, select “VIVOTEK Vast2” as the VMS Profile.


9. Enable “Disaster Recovery” if you want ALL your camera data to be replicated.


10. Enable “Storage Extension” if you want free up local disk space as camera data is aging (or how full your local drive gets).


11. When ready, click on “Resume” to begin the replication process.


12. You can monitor real time progress and status by opening the Properties dialog and selecting the Bridge tab.


13.  You can also monitor the status of individual files by looking at the overlay icons.


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