Tiger Bridge 5.0.2 Release Notes
Fixed Known Issues in Version 5.0.2
Upgrading to Tiger Bridge 5.0.2
Unresolved Known Issues

February 2, 2023

This document provides release information about version 5.0.2 of Tiger Bridge. It discusses fixes andunresolved known issues in this release.

Fixed Known Issues in Version 5.0.2
Importing All Data on Sync with Target
Tiger Bridge 5.0.2 includes improvements ensuring that all needed data is synchronized on initial pairingof the source with the target or when synchronizing sources through a common target.

Tiger Bridge Explorer Fixes
To prevent instability of the Tiger Bridge Explorer, in version 5.0.2 all buttons remain inactive until you
select a file or folder in the Explorer.

Faster Initial Scan of Sources
Tiger Bridge 5.0.2 further speeds up the initial scan of your sources on startup.

Synchronizing Tiger Bridge with the Target’s Own Archiving Policy
In order to reduce the costs generated when checking whether a file is moved to the archival tier of thetarget by its own archiving policy, Tiger Bridge 5.0.2 reports that a file is archived immediately after thepolicy’s timeout elapses.

Improved Handling of Read Only Files on an NFS Share Source
Version 5.0.2 resolves problems, which could occur when handling Read Only files stored on an NFS
network share source.

Improved Connectivity to S3-compatible Targets
Version 5.0.2 resolves problems that could prevent you from establishing connection to your S3compatible target when providing the access credentials.

Stub File Improvements
Tiger Bridge provides the following stub file improvements:••

you can now change the stub file attributes
you can handle Read Only stub files without causing system instability

Improved Support for DWG Files Synchronization
Version 5.0.2 prevents cases in which synchronized computers on which a DWG file is opened forpreviewing only lose access to it when changes are introduced and saved to the file on anothercomputer.

Improved Collaboration with Antivirus Programs
Concurrent request for access to a managed file’s stream from Tiger Bridge and the antivirus program
could lead to temporary file system deadlock. Version 5.0.2 includes improvements that prevent suchconflicts and prevent file system delays caused by them.

Upgrading to Tiger Bridge 5.0.2
To upgrade Tiger Bridge to this new version, you should simply run the installation of version 5.0.2 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 secondversion 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.