Wasabi Surveillance Cloud - FAQs
    • 22 Nov 2024
    • 29 Minutes to read
    • PDF

    Wasabi Surveillance Cloud - FAQs

    • PDF

    Article summary

    Which VMS vendors are supported by Wasabi Surveillance Cloud (WSC)?

    VMS vendors currently supported by WSC are:

    Manufacturer

    VMS Product(s)

    Avigilon

    Control Center

    Axis

    Camera Station

    Digifort

    DGF (all versions)

    Digital Watchdog

    Spectrum

    exacq

    Vision (all versions)

    Flir

    United

    Genetec

    Omnicast

    Hanwha

    Wisenet WAVE

    Identiv

    VisionPoint/VelocityVision

    ipConfigure

    Orchid Fusion

    Lenel

    VRx

    Milestone XProtect

    XProtect

    Network Optics

    Nx Witness

    Panasonic

    Video Insight

    Qognify

    VisionHub, Cayuga, Ocularis, NiceVision

    Safety Vision

    Foresight Pro, DVMS PRO, PrimaView

    Salient

    Complete View

    Siemens

    Surveillance Video

    Verint

    Edge

    Vivotek

    VAST

    How much bandwidth do I need with WSC?

    WSC replicates video surveillance data generated from surveillance cameras stored on a local storage system to Wasabi. This data traverses the Windows machine on which the WSC software is hosted.

    To quickly estimate your required internet speed, you can use the “1/5 rule of thumb”:

    • If you know the average bitrate of all your cameras:
      Multiply total recording bitrate x 1.5 (allows for read back and fluctuations)

      Example: 173 Mbps x 1.5 = ~250 Mbps
    • If you know the current storage requirements for a given retention period:

      Multiply #GB / #days x 0.15

      Example: 350 GB per day = 350 x 0.15 = ~50Mbps, 100TB per month = 100 x1024 x.15 ÷ 30 = ~500 Mbps

    Throttling the Bandwidth Usage of WSC Software

    Bandwidth can be set to a limit or scheduled, as long as enough bandwidth is available to upload. Otherwise, WSC will always fall behind, resulting in data loss in situations where all data is not backed up to Wasabi.

    The number of threads used to upload data can be reduced, or WSC can be paused during certain hours to avoid replication.

    1. Run "regedit" (Registry Editor) on the Windows host machine.
    2. Navigate to KEY: HKEY_LOCAL_MACHINE\SOFTWARE\Wasabi\tiger-bridge\tiersvc\settings
    3. Look for value: work_threads_count
    4. Choose a value between 1 and 16. (A value of 1 will throttle to ~50-100 Mbps upload depending on your system, cloud, and connection. A value of 16 will saturate a one Gbps pipe.)
    5. After changing the number, restart the WSC services from the Windows Services app.

    How do I schedule bandwidth throttling using WSC?

    With the following command, the Global Worker Threads used by WSC can be adjusted depending on network bandwidth usage. Open CMD to run the following command (there is no need to restart services after running this command):

    tiercli config global workers xx

    where xx is the number of active threads you want (leave empty to see the current configuration). For example:

    Use Task Scheduler to create two tasks to run on the schedule to increase and decrease the workers' thread count.

    1. Open the Task Scheduler.

    2. Create your task, giving it a unique name. Select the option to Run whether the user is logged on or not. Select the option to Run with highest privileges.

    3. Create a trigger schedule for the command to run to lower/raise the threads.

    4. Specify your action. Select "Start a program." Click Browse and navigate to CMD. Run CMD with the Command/Argument:
      /k tiercli config global workers 4

    5. You can change the number of threads from 4 to a different number between 1 and 16 if you want the task running during the day/peak network traffic hours. Click OK to save and you will be prompted for the Administrator password.

    6. Repeat the steps above to create a task to raise the threads for the evening schedule.

    You should have two tasks created for lowering the threads during the day and then raising them at night.

    What network ports do I need to open up to run WSC?

    WSC software runs on Windows OS only and requires the following ports open (inbound and outbound):

    TCP Ports 443, 8536, and 8537

    WSC uses port 443 to connect to the Wasabi object storage via S3 protocol, and the licensing server. WSC uses ports 8356 and 8357 to communicate with the configuration service.

    When is the data in the WSC account deleted?

    Data uploaded to the cloud is extremely safe with WSC. Data in the cloud is deleted automatically when the corresponding local file is deleted (that is, when the VMS deletes the file after the retention period has been reached or if someone deletes camera files locally).

    Deleting a connection between a source and a target does not delete any data in the cloud. A warning message lets you know when you are about to end up with orphan stub files (in case you want to retrieve any associated data back from the cloud before deleting the pair). As long as the bucket remains untouched in the cloud, it is always easy to reconnect to regain access to your data.

    If you want to test the disaster recovery, always delete the source-pair association (Delete Source) to break the connections with the cloud before deleting any local file. Also, if you delete files in the cloud bucket directly, the WSC will not be aware and assume that the data is still there. The WSC will not replicate these files again and assumes that any local stub files still point to the valid data.

    How do I perform DR Restoral with WSC?

    WSC offers a critical DR feature, allowing you to restore your metadata and archived footage to your on-premise hardware in case of a server or hard drive failure. 

    If your server has crashed and needs to be replaced, you will need to install and configure the VMS software, and then install the WSC software on the new machine before being able to perform a DR of your data.

    In case of hard drive failure only, that was storing your archived footage, replace the bad hard drive, and you are ready to set up a new source for the DR.

    The steps below are for any VMS except Milestone XProtect (as WSC is integrated directly and has its procedures).

    1. Click Add Source.

    2. Specify the new drive and folder where you want to restore your metadata or footage.

    3. Input your Wasabi information, select the bucket where your recordings were stored, and click Apply.

    4. When performing a DR, you will be prompted with the following options to choose an action that needs to be performed on any existing data in the target. Choose one and click OK.

    A success message will inform you that the DR has begun.

    You will see your existing folder structure created. 

    All the existing stub files will be reindexed to your file system.

    Notes:

    1. Depending on the number of cameras, folders, and recordings you stored, the time to reindex all of your metadata or footage can vary based on the size/amount of files and/or the speed of your ISP.
    2. Upon restoring your metadata and/or archived footage, depending on your VMS software, you may be required to reindex the video files to the VMS database either directly through your VMS software or by using the SQL database.
    If you want to test the disaster recovery, always delete the source-pair association (Delete Source) to break the connections with the cloud before deleting any local file. Also, if you delete files in the cloud bucket directly, the Wasabi Surveillance Cloud will not be aware and assume that the data is still there. The Wasabi Surveillance cloud will not replicate these files again and assumes that any local stub files still point to the valid data.
    Deleting an Active Source will prompt you to confirm the action. The prompt will also provide the amount of stub files that will become unusable.

    How do I perform a DR with XProtect and the WSC?

    WSC allows you to enable the DR of your recording drive. When the DR option is enabled, WSC can recover from a recording storage or archive failure. When XProtect detects the failure, WSC will display a warning message. It is critical to follow the step-by-step instructions provided.

    Recovering a Failed Recording Driver After the Disaster

    1. When all servers are Online OR Healthy, green status icons are displayed. For example:

    2. Once WSC recognizes that a recording drive has failed, it will automatically alert of a Disaster Recovery scenario.

    3. Connect a replacement drive to the recording server, but do NOT mount it. To be safe, the replacement drive should NOT be formatted (or you should FIRST STOP the recording server PRIOR to connecting a formatted drive).

    4. Click Disaster Recovery Wizard to begin the recovery process. Click Next.

    5. The Wizard will first stop the recording server (if it is not already). Click Next.

      The service will be stopped. 

    6. It is time to format and assign the original drive letter to the replacement drive (in this example, the failed drive letter was E:).

    7. Install and partition your new drive and be sure to format it to use the same volume letter as the previous failed drive.

       

      When the replacement volume is detected with the proper drive letter, the surveillance bridge displays a green checkmark:

    8. WSC will ask for confirmation. Click Next.

      WSC will restart the services.

    9. The Wizard is complete and you can click Finish.

    You can view the restore job in the Administration tab under the Recording server that had the failed recording drive.

    Recovering a Failed Recording Server After the Disaster

    When the Disaster Recovery option is enabled, WSC can recover from a recording server failure. When XProtect detects the failure, WSC will display a warning message. It is critical to follow the step-by-step instructions provided.

    1. Green status icons are displayed for all the servers that are online and healthy:

      Click Disaster Recovery Wizard to engage the recovery procedure.

    2. Make sure the replacement recording server is ready and available:

    3. WSC automatically lists the available replacement servers. Select one and click Next.

    4. Activate the WSC license on the replacement server.

      The Wizard will stop the replacement recording server.

    5. It is necessary to format and assign the same drive letter to the replacement drive (in this example, the original drive letter was E: ).

    6. Make sure you create a new disk and format it to have the same volume letter.

       

      When the replacement volume is detected with the proper drive letter, WSC displays a green checkmark:

    7. Click on Next and the recovery will begin.

    8. The Wizard has completed. Click Finish.

    9. You can now verify the recovery completed by clicking the Administration tab and selecting the recording server that you recovered to. Then you will see the Job Completion tab.

    How do I schedule Replication with WSC?

    WSC allows you to leverage the Windows task scheduler to schedule replication and offload video data when the network bandwidth is limited. To configure a task scheduler, perform the following steps.

    Pause the Replication Task Scheduler

    1. Open the Task Scheduler.

    2. Click Action on the top menu. Click Create Task.

    3. On the General tab, fill out the Name as Pause WSC Replication. Select the option to Run whether the user is logged on or not. Select the option to Run with highest privileges.

    4. Click the Triggers tab. Click New...

    5. Specify when you want WSC to pause/stop replicating data to your Wasabi Bucket.
    6. Select any advanced settings depending on your specific scenario. Click OK.

    7. Click the Actions tab. Click New...

    8. From the Action drop-down, select Start a program.

    9. Click Browse and select this location: C:\Program Files\Wasabi\Wasabi Surveillance Cloud\tiercli.exe
    10. Add these arguments: op pause s

    11. Click OK. Click OK again.
    12. Enter the local administrator password. Click OK.

    13. When you click Task Scheduler Library in the left-hand pane, you will see your task listed.

    14. If you open WSC, you should see it switch from a Running state to a Paused state as the schedule is met.

    Resume Replication Task Creation

    1. Go back to the Task Scheduler. Click Action from the top menu. Click Create Task.

    2. On the General tab, enter the Name as Resume WSC Replication. Select the option to Run whether the user is logged on or not. Select the option to Run with highest privileges.

    3. Click the Triggers tab. Click New...

    4. Specify the date and time you need WSC to replicate the data to your Wasabi Bucket.
    5. Select advanced settings depending on your specific scenario. Click OK.

    6. Click the Actions tab. Click New...

    7. From the Action drop-down, select Start a program.

    8. Click Browse and select this location: C:\Program Files\Wasabi\Wasabi Surveillance Cloud\tiercli.exe
    9. Add the arguments: op pause none

    10. Click OK. Click OK again.
    11. Enter the local administrator password. Click OK.

    12. Click Task Scheduler Library in the left-hand pane to view all the tasks you created.

    13. As the schedule for Resuming the replication is met, you will see that the WSC application goes from Paused to Running.

    How do I virtually extend a drive to use with the WSC?

    WSC allows you to "virtually extend" your Windows drive when the VMS software you are using does not recognize that the archived video data is being offloaded to Wasabi and reports that the drive is full.

    Follow the steps below to virtually extend the drive size so the VMS software recognizes the overall storage size that you intend to use to meet your retention requirements.

    1. Open a Windows Explorer window and navigate to your storage drives. Here you can see the size of your current Windows drives. For example:

    2. Within the VMS, you should be able to specify the Windows drive and location that you want to use for your recording storage and the utilization of the drive. The VMS should reflect the size of the current Windows drive.

    3. Open WSC and make sure that you have WSC configured to be pointing to the drive that your video archives are recording to. This will also affect which Windows Drive gets virtually extended to the new size that you specify in the registry key.

    4. Make a registry key creation open the Windows registry editor (type "regedit" in Start Menu, Run or CMD).
    5. Navigate to Computer\HKEY_Local_Machine\System\CurrentControlSet\Services\tierflt.
    6. Create a REG_DWORD and name it "VirtualExtensionSize".
    7. Modify the newly created DWORD and change its value to the desired volume size in GBs and be sure to select "Decimal". For example, if you want to achieve 30 days of retention with 2 days being on-premise and 28 days being in the cloud you need to specify how much overall storage 30 days will consume. If each day requires 1 TB of storage, then you would specify 30,000 GBs or 30 TBs of virtual drive space.

      Note: This is only a virtual extension and not a real one. In reality, the volume will retain its original size, but Windows will report it as 30 TBs to any application such as the VMS software that may want to access it.

      Your registry entry should look like the following highlighted entry:

    8. After creating the value and exiting out of the registry editor, you can restart the machine for the changes to take effect or restart WSC services via the command prompt.
    9. If you want to avoid restarting the machine, you can run the following command lines in an administrative CMD:

       - net stop tiersvc - net stop tierflt - net start tierflt - net start tiersvc

      These command lines will restart WSC's main service as well as the tiering filter driver in the correct order.

      Note: If the services don't stop or error out then you will need to restart the server in order for the changes to take effect.

    10. Now, when you refresh your Windows Explorer window,  your drive sizes will show/report 30 TBs in size for your recording drive that you have connected in WSC.

    11. When you check your VMS Software it should also reflect this change and report the new available recording storage amount. If not, you may need to restart the VMS services to refresh the storage reporting.

    How do I use AXIS Camera Station with the WSC?

    AXIS Camera Station  is validated for use with the WSC. AXIS Camera Station is a video and access management software developed to fit surveillance use cases.

    Prerequisites

    WSC Installation

    For activation and installation of WSC software instructions, refer to the following Knowledge Base article. After installing WSC, you need to edit a registry key to virtually extend the volume size of your recording volume so that ACS recognizes the overall size requirement.

    1. Open the Windows registry editor and type "regedit" in the Start Menu, Run, or CMD
    2. Navigate to Computer\HKEY_Local_Machine\System\CurrentControlSet\Services\tierflt
    3. Create a REG_DWORD and name it "VirtualExtensionSize"
    4. Update the newly created DWORD and change its value to the desired volume size in GB (decimal) as needed. For example, putting "500" would extend the volume to 500 GB. Of course, this is only a virtual extension and not a real one. In reality, the volume will retain its original size, but Windows will report it as 500 GB to any application that may want to access it
    5. Restart the machine for the changes to reflect. If you want to avoid restarting the machine, you can run the following command lines in an administrative CMD:

      net stop tiersvc net stop tierflt net start tierflt net start tiersvc

      These command lines will restart WSC's main service as well as the tiering filter driver in the correct order. Your registry entry should look like the following:

    AXIS Camera Staton Cconfiguration

    1. Install, configure, and activate your AXIS Camera product.
    2. After creating a bucket on Wasabi, go to your AXIS Camera Station client and look for the main recording drives by navigating to configuration>management. Here you can adjust allocated capacity.

    3. Under configuration selection make sure the cameras you wish to store in the cloud are storing the drive you plan to replicate.

    Wasabi Surveillance Cloud Configuraiton

    1. Launch the WSC app.
    2. Using the Add Source button, select the same drive/folder as shown in AXIS Camera Station as the source to be replicated.

    3. Click 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.

    4. Select the appropriate region where you want to store the video recordings.
    5. Click on Create Bucket to create a new bucket in your WSC account. Use the bucket naming conventions specified here. Click OK when done.

    6. Click Apply to apply the configuration changes.

    7. The Surveillance Cloud software is now set to begin replicating all the data in the source folder to the Wasabi bucket. After all configuration steps have been performed, click the “Resume” button (first click on WSC at the top left) to start the service. The data replication to the cloud begins immediately.

    8. Log on to the Wasabi console to confirm the data is being written to the bucket with the same directory structure as the source.

    Additional Configuration Information

    DR Policy: Copies the customer data to the cloud from the local folders. Both data sets are identical (the one on-premise, and one in the cloud). The bridge makes a full copy of data from the local directory to the cloud for redundancy.

    Storage Extension Settings: This setting extends 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-premise capacity, but data is still in the cloud and accessible anytime it is needed.

    DR + Storage Extension: If both options are enabled, data gets replicated to the cloud when the data is added to the disk. Data is only deleted from the local drive based on the specified retention period. Data won't be available on the local drive but an still be retrieved instantly from the cloud.

    How do I use Digital Watchdog DW Spectrum VMS with WSC?

    DW Spectrum is validated for use with the WSC. DW Spectrum is an open-platform video management solution.

    Prerequisites

    Reference Architecture Diagram>

    Configuration

    Note: The Configuration Wizard steps explained on the installation article above will serve the same purpose as the steps explained below.

    1. Launch the WSC app.
    2. Click on Global Settings and then select "Digital Watchdog - Spectrum" profile from the VMS Profile drop-down options, as shown below.

    3. Click on WSC to expose the Add Source button. Using the Add Source button, select the drive/folder with the DW video recordings as the source to be replicated.

    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.

    5. Select the appropriate region in which you want to store the video recordings. Click on Create Bucket to create a new bucket in your WSC account. Use the bucket naming conventions specified here. Click OK when done.

    6. Click Apply to apply the configuration changes.

    7. 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.

    8. 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

    DR Policy: Copies the customer data to the cloud from the local folders. Both data sets are identical (the one on-premise, and one in the cloud). The bridge makes a full copy of data from the local directory to the cloud for redundancy.

    Storage Extension Settings: This setting extends 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-premise capacity, but data is still in the cloud and accessible anytime it is needed.

    DR + Storage Extension: If both options are enabled, data gets replicated to the cloud when the data is added to the disk. Data is only deleted from the local drive based on the specified retention period. Data won't be available on the local drive but can still be retrieved instantly from the cloud.

    How do I use Hanwha Wisenet WAVE VMS with the WSC?

    Hanwha's Wisenet WAVE is validated for use with the WSC. Wisenet WAVE is an IP Video management platform that allows users to create IP video surveillance solutions.

    Prerequisites

    Configuration

    1. Install, configure, and activate WAVE VMS product if you don't have one already.
    2. Launch the Wasabi Surveillance Cloud app.
    3. Using the Add Source button, select the archive to be backed up/moved to Wasabi Cloud storage using the Add Source button.

    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.

    5. Select the region where you want to store the video recordings. Click on Create Bucket to create a new bucket in your WSC account. Use the bucket naming conventions specified here. Click OK when done.

    6. Click Apply to apply the configuration changes. The Surveillance Cloud software is set to begin replicating all the data from the source folder to the Wasabi bucket. After all configuration steps have been performed, click the “Resume” button (first click on WSC at the top left) to start the service. Data replication to the cloud will commence immediately.

    7. Log on to the Wasabi consoleand confirm the data is being written to the bucket with the same directory structure as local storage.

      Note: No configuration is needed in Wisenet Wave VMS to use WSC software and Wasabi Hot Cloud storage.

    Additional Configuration Information

    DR Policy: Copies the customer data to the cloud from the local folders. Both data sets are identical (the one on-premise, and one in the cloud). The bridge makes a full copy of data from the local directory to the cloud for redundancy.

    Storage Extension Settings: This setting extends 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-premise capacity, but data is still in the cloud and accessible anytime it is needed.

    DR + Storage Extension: If both options are enabled, data gets replicated to the cloud when the data is added to the disk. Data is only deleted from the local drive based on the specified retention period. Data won't be available on the local drive but can still be retrieved instantly from the cloud.

    How do I use Milestone XProtect with the WSC?

    Wasabi Surveillance Cloud is validated for use with Milestone XProtect Video Management SoftwareXProtect's flexible open platform allows you to scale your video solutions.

    Video on Getting Started With WSC & Milestone xProtect.

    Prerequisites

    DR/Replication Configuration

    1. Start the Milestone XProtect Management Client application. Click on the Disaster Recovery option in the site navigation menu, and then click on Enablein the right window. See the screenshot below for reference.

    2. Provide the following information:

      Server URL - Set this to the appropriate region service URL (Use Wasabi Service URLs for reference),
      Access Key - Paste your WSC Account access key here.
      Secret Key- Paste your WSC Account secret key associated with the access key above, here.

      Click on List buckets and select the bucket you want to use as the target for the recordings. Click "OK" when done.

      Note: Select a DIFFERENT bucket/container for EACH volume.

      Note: This configuration example refers to Wasabi's us-east-1 storage region. To use other Wasabi storage regions, please use the appropriate Wasabi service URL as described in our Wasabi Service URLs.

    3. To start the replication process, switch the “Inactive” to “Active” (top right). Within a few minutes (depending on the number of managed cameras and files), the WSC software replicates and displays the % of local data replicated to the cloud.

      Note: 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.

    Congifuration for the Storage Extension

    1. Use the extension option to make your local volume appear bigger and infinitely scalable. This functionality can be activated on your recording storage(s),  Archive(s), or both. It can be activated with or without Disaster Recovery. When DR is activated, the extension uses a subset of the data that is already replicated on the DR target. Select the WSC “Extension” tab.

      Note: For each volume where Extension is desired, click “Enable" as shown above.

    2. If Disaster Recovery has already been configured for this volume, you will NOT be prompted for your storage account details as your data does NOT get replicated twice. The same bucket will be used. Make sure to select a DIFFERENT bucket for EACH volume.
    3. Select the “By Age” option to keep camera data locally for a specific time or select the “By Size” option to keep it until your local drive reaches a specified capacity threshold. When either condition is met, content is removed and replaced by zero-byte stub files. Data is safely kept in the Wasabi bucket until the retention time set on your storage volume is met. Maintain enough “free” space on your recording drive to ensure Milestone has enough room to continue recording during an internet outage.

    4. To start the replication process, switch from “Inactive” to “Active” (top right). It takes a minute for the Surveillance Cloud to display the % of local data replicated to the cloud.

    Smart Client Video Playback

    1. To review or playback video(s) stored in your Wasabi Cloud bucket, log into the Milestone Smart Client application and simply play back the period you need to review.

    2. You can review the status and location of the video on the timeline by looking at the legend information and the current color of the video selection being played back.

    Additional Configuration Information

    DR Policy: Copies the customer data to the cloud from the local folders. Both data sets are identical (the one on-premise, and one in the cloud). The bridge makes a full copy of data from the local directory to the cloud for redundancy.

    Storage Extension Settings: This setting extends 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-premise capacity, but data is still in the cloud and accessible anytime it is needed.

    DR + Storage Extension: If both options are enabled, data gets replicated to the cloud when the data is added to the disk. Data is only deleted from the local drive based on the specified retention period. Data won't be available on the local drive but can still be retrieved instantly from the cloud.

    How do I use Network Optix Nx Witness VMS with the WSC?

    Network Optix Nx Witness VMS is validated for use with Wasabi Surveillance Cloud. Network Optix works with companies to create full-stack (Desktop, Server, Mobile, and Cloud) intelligent IP Video software products like Nx Witness VMS.

    Prerequisites

    Reference Architecture Diagram

    Configuration

    Note: The Configuration Wizard step explained in the installation article above will serve the same purpose as the steps listed below.

    1. Install, configure, and activate your Nx Witness VMS or other Powered by Nx software product.
    2. Launch the WSC application, click on the Global Settings, and then select the "Network Optix - NX Witness" profile from the VMS Profile drop-down options as shown below.

    3. Click on the WSC to expose the Add Source button. Using the Add Source button, select the drive/folder with the video recordings as the source to be replicated. Users can choose the entire archive, high-quality, low-quality, or even individual cameras as needed.

    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.

    5. Select the region where you want to store the video recordings. Click on the Create Bucket to create a new bucket in your WSC account. Use the bucket naming conventions specified here. Click OK when done.

    6. Click Apply to apply the configuration changes.

    7. The surveillance cloud software is now set to replicate the data from the source folder to the Wasabi bucket. To start the service, click on the resume button. Replication begins immediately once the service is resumed.

    8. Log on to the Wasabi console to confirm the data is written to the bucket with the same directory structure as the source folder.

    Additional Configuration Information

    DR Policy: Copies the customer data to the cloud from the local folders. Both data sets are identical (the one on-premise, and one in the cloud). The bridge makes a full copy of data from the local directory to the cloud for redundancy.

    Storage Extension Settings: This setting extends 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-premise capacity, but data is still in the cloud and accessible anytime it is needed.

    DR + Storage Extension: If both options are enabled, data gets replicated to the cloud when the data is added to the disk. Data is only deleted from the local drive based on the specified retention period. Data won't be available on the local drive but can still be retrieved instantly from the cloud.

    How do I use Salient CompleteView VMS with the WSC?

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

    Prerequisites

    Configuration

    1. WSC should be installed on the same server where CompleteView recording server is installed. Iinstall the WSC software on each server in case multiple recording servers are deployed. The same credentials can be used across all servers. Launch the WSC app to set the configuration.
    2. Select the folder you defined in CompleteView as a Volume by clicking the “Add Source” button. Add each folder separately if more than one Volume has been configured in CompleteView. Do not add sub-folders whose parent folder has been added as a source.

    3. 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.

    4. Select the region where you want to store the video recordings.
    5. Click Create Bucket to create a new bucket in your WSC account. Use the bucket naming conventions specified here. Click OK when done.

    6. Click Apply to apply the configuration changes.
    7. The Surveillance Cloud software is set to replicate all the data from the source folder to the Wasabi bucket. After all configuration steps have been performed, click the “Resume” button (first click on Wasabi Surveillance Cloud at the top left) to start the service. Data replication to the cloud commences immediately.

    8. Log on to the Wasabi console to confirm the data is written to the bucket with the same directory structure as the source folder.

    Additional Configuration Information

    DR Policy: Copies the customer data to the cloud from the local folders. Both data sets are identical (the one on-premise, and one in the cloud). The bridge makes a full copy of data from the local directory to the cloud for redundancy.

    Storage Extension Settings: This setting extends 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-premise capacity, but data is still in the cloud and accessible anytime it is needed.

    DR + Storage Extension: If both options are enabled, data gets replicated to the cloud when the data is added to the disk. Data is only deleted from the local drive based on the specified retention period. Data won't be available on the local drive but can still be retrieved instantly from the cloud.

    How do I use Vivotek VAST Security Station with the WSC?

    Vivotek's VAST Security Station (VSS) has been validated for use with the WSC. VIVOTEK’s VAST Security Station (VSS) is an easy-to-use, all-around, AI-powered IP video surveillance software designed to help you manage tens of thousands of cameras and focus on only what matters to you through VIVOTEK AI solutions.

    Prerequisites

    Configuration

    1. After installing VAST Security Station software log into VSS.

    2. Go to the settings page by clicking on the "gear" icon in the upper right-hand and then click "Settings".

    3. Click on "Recording Options".

    4. From the Recording Management screen, specify the default recording location to archive your video and recording schedule/retention period for your cameras.

    5. Install the WSC software. Refer Knowledge Base article to activate and install the WSC software instructions. Note - When installing the software, select the VAST Security Station option from the VMS Profiles list.

    6. Once the software is installed and running, create your source and point it to the location specified inside the Recording Management options.

    7. Within WSC, you can turn on the DR Policy. You can also turn on Storage Extension and configure that setting depending on how much data you want to keep on-premise and how much you want to push to Wasabi. In the example below, you can see that after 1 hour of being on-premise, the recordings are offloaded to Wasabi. For more information on DR and Storage Extension settings, refer to the "Additional Configuration Information" section below.

    8. To playback a video, you can review all videos through the Playback settings inside the VSS Client. You can natively scrub through the timeline and play the video seamlessly.

    9. If you navigate to your recording folder, you can see the data replicated or reclaimed by Wasabi Surveillance Cloud. The White Cloud icons indicate the data within that folder has been offloaded to Wasabi and the on-premise storage has been reclaimed. The Green Cloud with the white check mark indicate that the data has been replicated to Wasabi and is available on-premise and in the Wasabi cloud.

    Additional Configuration Information

    DR Policy: Copies the customer data to the cloud from the local folders. Both data sets are identical (the one on-premise, and one in the cloud). The bridge makes a full copy of data from the local directory to the cloud for redundancy.

    Storage Extension Settings: This setting extends 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-premise capacity, but data is still in the cloud and accessible anytime it is needed.

    DR + Storage Extension: If both options are enabled, data gets replicated to the cloud when the data is added to the disk. Data is only deleted from the local drive based on the specified retention period. Data won't be available on the local drive but can still be retrieved instantly from the cloud.


    Acronyms

    VMS - Video Management Systems

    WSC - Wasabi Surveillance Cloud

    WCN - Wasabi Cloud NAS (Network attached storage)

    TCP - Transmission Control Protocol

    DR - Disaster Recovery

    CMD - Command Prompt

    ISP - Internet Service Provider

    VSS - Vivotek VAST security station



    ESC

    Eddy AI, facilitating knowledge discovery through conversational intelligence