Tiger Bridge 5.0 Release Notes
What’s New
Upgrading to Tiger Bridge 5.0
New Known Issues
Unresolved Known Issues

July 25, 2022

This document provides release information about version 5.0 of Tiger Bridge. It discusses new features
as well as fixed and unresolved known issues in this release.

What’s New
Tiger Bridge Explorer
The Tiger Bridge Explorer is a graphic interface browser, which allows you to explore the contents ofyour sources filtering the results by source, data status and target tier. You can download the results
displayed for a browsed path as a list in a text file.
You can also use the Tiger Bridge Explorer to perform manual lifecycle operations, including bulk
operations on multiple files with the same status. You can also quickly open a browsed path in WindowsExplorer.

Advanced Monitoring
Version 5.0 focuses on providing you with multilevel options for monitoring the status of Tiger Bridge,managed data and operations:
••

•

•
•
•

Tiger Bridge tray icon – as a first-level interface, the tray icon status gives you information about
Tiger Bridge (running, paused, not activated) and the status of the automatic replication queue(complete, running, failed).
File and folder icon overlays – version 5.0 introduces a new set of icon overlays covering moredata states including transitional ones ( queued for replication and failed replication, forexample). The new set of overlays also distinguishes between the expected monitoring purposes
depending on whether you have configured your sources with automatic replication (allowing
you to easily locate data that is not yet replicated) or without automatic replication (allowing
you to easily locate data that you have manually replicated).
Note: You can configure Tiger Bridge to use the icon overlays with their legacy states.
The Tiger Bridge Configuration – selecting a source in the Configuration shows you thepercentage of replicated data on it and lets you to easily open the Bridge tab of the source’s
Properties dialog and view more detailed information about data in the source folder.
Event Viewer – Tiger Bridge 5.0 provides improved integration with Windows Event Viewer andpops up a system message about the status of each manually performed operation.
Properties dialog in Windows Explorer – the Bridge tab now displays statistics about the root ofa source volume.
Source folder icon in Windows Explorer – Tiger Bridge displays a folder configured as a sourcewith a Tiger Bridge logo icon to let you easily distinguish between source folders and otherfolders in Windows Explorer.
Note: When the root of a volume is configured as a source, the default volume icon is displayed.

Versioning Policy
With Tiger Bridge 5.0 you can control the number of replicated versions of the same file on the target.
By configuring a Versioning policy, you can limit the number of file copies kept on the target using eitherof the following two parameters:••

Deletes all copies that are older than a specified time interval.
Deletes all copies exceeding a specified number, starting from the oldest ones.

For more details about adding and configuring a Versioning policy, refer to the Tiger Bridge 5.0 Guide.

Soft Delete Policy
To allow you to undelete data from your source, when it is paired with a target that does not supportversioning, Tiger Bridge 5.0 introduces a Soft Delete policy. The policy configures by how long to offset
the synchronization of the file deletion on the target. Within that time interval, you can manually
undelete any file.

Revert File Modifications
Using the Tiger Bridge shell extension context menu, you can easily revert a modified file on your source
to its last replicated state.

Manually Replicate Data to a Selected Tier on AWS S3 and Azure Targets
With version 5.0 when replicating data manually through the Tiger Bridge shell extension you can selectthe target tier to which to replicate it.

Support for New Targets
With Tiger Bridge 5.0 you can use ORockCloud and Symply NEBULA as data replication targets. For
specific prerequisites, refer to the Tiger Bridge 5.0 Administration Guide.

Support for AWS S3 Glacier Instant Retrieval Storage Class
Tiger Bridge 5.0 adds support for S3 Glacier Instant Retrieval storage class. You can use it as default
storage class for automatic replication or replicate data manually directly to it using the Tiger Bridge
shell extension.

Support for Windows® 11/Server 2022
You can install Tiger Bridge 5.0 and any of its add-ons on computers running Microsoft Windows
11/Server 2022.

Support for Azure Blob Versioning
With version 5.0 you can use both Azure blob snapshots and blob versioning, when you want to benefit
from the Tiger Bridge versioning and Undelete functionalities.

Dropped Support for AWS Access Key Rotation
To use Tiger Bridge 5.0 with an AWS target, access key rotation must be disabled.

Upgrading to Tiger Bridge 5.0
To upgrade Tiger Bridge to this new version, you should simply run the installation of version 5.0 on thecomputer running Tiger Bridge. All configuration settings will be preserved after the upgrade.

New Known Issues
Displaying the Tiger Bridge Tray Icon
In some cases, after upgrading to version 5.0 the Tiger Bridge tray icon may not show initially. To resolvethe problem, you should either restart the computer one more time after the upgrade or manually start
it by double-clicking tier_tray.exe in the Tiger Bridge installation folder.

Using the Command-line Interface to Activate a SaaS License with New Credentials
If you have changed the credentials of your SaaS order and need to re-activate Tiger Bridge using thecommand-line interface, before executing the activation command with the new credentials you must
deconfigure the license using the following command:tiercli license saas deconfigure

When re-activating your SaaS license in the Configuration, you should simply enter the new credentials
in the Activation dialog.

Unresolved Known Issues
Deleting Files from the Target When the Source is a Folder
Normally, regardless of the replication target type, as long as the “Delete replica when source file isremoved” option is enabled, when you delete one or more files from your source, they are also deleted
from the target. When this option is enabled and your target is a local volume or a network share, adeleted folder on your source will not be deleted from the target, unless you permanently delete it fromthe source i.e., empty the Recycle Bin. With object storage targets, a folder moved to the Recycle Bin orpermanently deleted is also deleted from the target, only if the whole volume is configured as a source.
If the source is just a folder on a volume, the folder will not be deleted from the object storage target.

Retrieving Offline Files from Google Cloud
Unlike other cloud targets, offline files stored on a Google Cloud target are directly retrieved on thesource when you attempt to open them or to manually rehydrate them.

Using Versioning Software on Azure Append/Page Blob
When using versioning on Microsoft Azure append or page blob as a target, you should keep in mind
that the first version of each file is not kept, and the second version overwrites it. From the second
version onwards, versioning works as expected on Azure append and page blobs.
A workaround to the problem is to introduce an insignificant change to the file after it has been initiallyreplicated on the Azure append/page blob (such as an added interval at the end of a text document, forexample) in order to trigger versioning for that file from that change onwards.