Tiger Bridge 5.0.1 Release Notes
What’s New
Fixed Known Issues in Version 5.0.1
Upgrading to Tiger Bridge 5.0.1
Unresolved Known Issues

November 17, 2022

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

What’s New
Enabled Target Versioning Verification
To prevent cases in which a new version of a file overwrites the previous one on the target because you
have enabled versioning just in Tiger Bridge, but not on the target, version 5.0.1 prompts you to check
whether versioning is enabled on the target on applying any of the Tiger Bridge versioning settings.

New Tiger Bridge Tray Icon Status
To allow you to better monitor the status of managed data through the tray icon, version 5.0.1 adds anew icon status designating that Tiger Bridge is retrieving data from the target or rehydrating files fromthe archive. For detailed description, refer to the Tiger Bridge 5.0.1 User’s Guide.

Retrieving Only Data Accessed Within Specified Time Period
When you use the command-line interface of Tiger Bridge 5.0.1 to retrieve nearline or offline files fromthe target, you can specify that only data accessed within a specified time period must be retrieved onthe source. For specific steps, refer to the Tiger Bridge 5.0.1 User’s Guide.

Specifying the Number of Threads Scanning NAS Sources on Startup
To speed up the initial scan of a NAS source on Tiger Bridge startup, in version 5.0.1 you can increase thenumber of threads used in the process by creating and managing a string value in the Tiger Bridge
registry. For detailed steps, refer to the Tiger Bridge 5.0.1 User’s Guide.

Preserving Files’ Security Descriptor Per Source
Instead of specifying whether all sources synchronized through a common target should keep the Active
Directory security descriptor of replicated files, with version 5.0.1 you can specify that the descriptor bekept on some sources and omitted on others. For the purpose you need to create a string value in theTiger Bridge registry. For detailed steps, refer to the Tiger Bridge 5.0.1 User’s Guide.

Specifying Additional Parameters of S3-compatible Targets
With version 5.0.1, when pairing a source with an S3-compatible target, you can specify additionalparameters such as the protocol signature version the target uses and whether to use virtual-hosted–
style or path-style URLs. For more information, refer to the Tiger Bridge 5.0.1 User’s Guide.

Manually Clearing the Windows Icons Cache
To allow you to resolve problems when the Tiger Bridge icon overlays are not properly updated after
upgrading to a new version, for example, in version 5.0.1 you can manually clear the icons cache ofWindows, by selecting the respective command in the Tiger Bridge tray icon menu.

Support for New Authentication Methods on Azure
When pairing a source with an Azure target, you can now choose to use a SAS token or SAS connection
string instead of account key when specifying the access to the designated Azure container. To use a SAStoken for access to the target, it must have all permissions enabled for the designated container.
Additionally, to use a SAS token for authentication, enter it in the Access Key field in the Configuration.
Currently, you can pair a source with an Azure container using a SAS connection string only through thecommand-line interface.

Fixed Known Issues in Version 5.0.1
Preventing Possible Data Loss on S3 Targets Due to Misconfigured VersioningFor Tiger Bridge versioning to operate properly, versioning on the target must be enabled as aprerequisite. With previous versions it was possible when versioning had not been enabled on an
Amazon S3 or S3-compatible target, the Tiger Bridge Versioning policy to perceive the only one andunversioned copy of a replicated file as an obsolete version and delete it. Tiger Bridge 5.0.1 resolves thisproblem.

Improved Support for FujiFilm Object Archive
Version 5.0.1 provides improved support for FujiFilm object archive target by improving the detection offiles moved among the target tiers by the target’s own archiving policy.

Reduced Errors for Manually Copied Files in a NAS Source’s Control Folder
Version 5.0.1 resolves a problem, which could populate the Tiger Bridge event log with errors about
inaccessible files in a NAS source’s control folder, when these files had actually been manually copied
there by the user.

Retrieving On Demand a Read Only Stub File
With version 5.0.1 you can retrieve from the target a Read Only file not only through the Tiger Bridge
shell extension, but also on demand, by double-clicking it on your source.

Improved Stability of Tiger Bridge Explorer
Version 5.0.1 improves the stability of Tiger Bridge Explorer when the Tiger Bridge service is not running.

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

Unresolved 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 resolve
the 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.

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.