Filter Options for the Disaster Recovery Policy and Storage Extension Settings
Wasabi Surveillance Cloud (WSC) provides filters for Disaster Recovery (DR) Policy and Storage Extension settings. Once enabled, these filters are applied to sources mapped to the bucket in the Wasabi Cloud through the WSC client. These filters can be enabled together for disaster recovery and storage extension.
Filter by date
Filter by name/location pattern
Filtering by Date
Using this filter, set up the DR policy or the storage extension settings to include or exclude data based on the creation or modification date of the files. Use “From” and “To” dates individually or in conjunction to target specific data. What to expect when these dates are provided:
If only the "From" date is provided, data from the specified date onwards will be subject to the DR policy or the Storage extension settings.
If only the "To" date is provided, data older than the specified date will be subjected to the DR policy or the Storage extension settings.
If both the “From“ and “To“ dates are provided, data created between the specified dates will be considered for applying the DR policy and Storage Extension settings.
Date filter refers to the “Last Write” date for an object. In NTFS, there is no modification date attribute. Available attributes are last write and last change. From and to dates refer to the Last Write Time attribute for applying the filters. When the content of the object is changed, the “last write” attribute is updated. If the name of the object is updated, the “last change” attribute will get updated. The last change attribute is not considered while applying the filters.
Note: Date filter refers to the “Last Write” date for an object. In NTFS, there is no modification date attribute. Available attributes are last write and last change. From and to dates refer to the Last Write Time attribute for applying the filters. When the content of the object is changed, the “last write” attribute is updated. If the name of the object is updated, the “last change” attribute will get updated. The last change attribute is not considered while applying the filters.
Filtering by Name and Location
Use this feature to include or exclude an object, file, or folder from applying the DR policy, or set the storage extension scope for surveillance data.
To enable this filter, specify the source path or Globally Unique Identifier (GUID) of the camera and add that to the "Exclude from operations" or "Include in operations" lists.
If the camera records data at C:\VideoRecordings\3ce48816-8f68-4d32-86ff-98ffb0cbd48d location, either "3ce48816-8f68-4d32-86ff-98ffb0cbd48d" or the entire path "C:\VideoRecordings\3ce48816-8f68-4d32-86ff-98ffb0cbd48d" can be specified to include or exclude for applying the sets.
Note: Changes to the Filter settings do not require a restart. However, the following conditions apply:
Changes made to the filters are updated by the service every minute.
Filter updates take effect after a minute.
Changes in the filters affect all items in the queue from the time a filter is updated.
Filter settings are not applied to the existing objects. Objects added to the queue after a filter is applied will follow the rules set up by the filter.
Example: There is a local source with 100 TB of data for replication (DR), and it's queued up and being processed. By enabling a filter to limit the data that gets replicated, the filter will be applied on newly queued data and disregard everything that was already in the queue.
The recommendation is to reload WSC's configuration or restart the “tiersvc” service after applying the filters. This ensures that the filter updates are in place.