Tiger Bridge 1.0 Administration Guide

Tiger Bridge 1.0 Administration Guide September 12, 2017

Copyright 2008-2017 Tiger Technology. All rights reserved. This publication, or parts thereof, may not be reproduced in any form, by any method, for any purpose. TIGER TECHNOLOGY MAKES NO WARRANTY, EITHER EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY IMPLIED WARRANTIES, OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, REGARDING THESE MATERIALS AND MAKES SUCH MATERIALS AVAILABLE SOLELY ON AN AS-IS BASIS. IN NO EVENT SHALL TIGER TECHNOLOGY BE LIABLE TO ANYONE FOR SPECIAL, COLLATERAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES IN CONNECTION WITH OR ARISING OUT OF PURCHASE OR USE OF THESE MATERIALS. THE SOLE AND EXCLUSIVE LIABILITY TO TIGER TECHNOLOGY, REGARDLESS OF THE FORM OF ACTION, SHALL NOT EXCEED THE PURCHASE PRICE OF THE MATERIALS DESCRIBED HEREIN. Tiger Technology reserves the right to revise and improve its products as it sees fit. This publication describes the state of this product at the time of its publication, and may not reflect the product at all times in the future. THIRD-PARTY TRADEMARKS All other brand names, product names, or trademarks belong to their respective holders. Title: Tiger Bridge Administration Guide Software version: Tiger Bridge 1.0 Date: September 12, 2017 Manual Revision and Control Revision Record Date Description Page Version 20 Jan. 2017 Initial Draft 12 Sept. 2017 Added support for Windows Server 2016. 7 1.0 12 Sept. 2017 TCP ports 8536 and 8537 should not be blocked by a firewall if any. 8 1.0

Table of Contents 1 Getting Started with Tiger Bridge 5 How It Works................................... 6 Install and Uninstall Tiger Bridge...................... 7 System Requirements.......................... 7 Storage Requirements.......................... 8 Install Tiger Bridge............................ 8 Uninstall Tiger Bridge........................... 9 Tiger Bridge Interface.............................. 9 Activate Tiger Bridge.............................. 10 2 Configure Tiger Bridge 11 Configuration Parameters........................... 12 Configure Tiger Bridge for Work with S3-compatible Object Storage 13 Configure Tiger Bridge for Work with IBM Cloud Object Storage 16 Configure Tiger Bridge for Work with Microsoft Azure Blob Storage 20 Configure Tiger Bridge for Work with DDN Web Object Scaler.. 23 Configure Tiger Bridge for Work with Network Share........ 26 Configure Tiger Bridge for Work with Local Volume Target.... 30 Configure Tiger Bridge to Work in Move Mode............. 32 Change Tiger Bridge Configuration Settings.............. 33 Disable Tiger Bridge............................... 34 3 Manage Advanced Settings 35 Delete File Behaviour.............................. 36 Minimum File Size for Replication...................... 37 File Restore Behaviour............................. 38 Specify the Processes Triggering File Restore............. 38 Partial File Restore Behaviour........................ 40 Enable/Disable Write-through on File Restore............. 40 Set File Restore Timeout............................ 41 3

Table of Contents Set Stub File Allocation Size Display Option............... 42 Set Stub File Head and Tail Sizes...................... 42 Set Startup Scan Wait Time......................... 43 Set Number of Parallel Threads during Data Replication...... 44 Manage Tiger Bridge Logs........................... 44 4 Manually Manage Data 49 Managing Data Through the Shell Extension.............. 50 Managing Data Through the Command-line Interface........ 52 Synchronize Data on the Source Volume and the Target...... 53 5 Appendix 55 Tiger Bridge CLI Commands List...................... 56 4

Getting Started with Tiger Bridge How It Works.............................. 6 Install and Uninstall Tiger Bridge................ 7 Tiger Bridge Interface........................ 9 Activate Tiger Bridge........................ 10

Getting Started with Tiger Bridge Congratulations on your purchase of Tiger Bridge, Tiger Technology s data lifecycle manager across storage tiers. Tiger Bridge pairs heterogeneous storage systems turning them into separate tiers of the same virtual storage unity. By automating the assignment of data to one or the other tier, Tiger Bridge allows users to address various workflow challenges. From alignment of data with storage costs, transparent data migration and synchronization between storage devices or geographically dispersed places, to extending your primary storage on the cloud and gateway to object storage. How It Works After you install Tiger Bridge on the designated computer you can pair together the source volume(s) with a target storage system, on which data will be replicated. You can use any already existing NTFS volume as a source volume and can pair it with one of the following targets: S3-compatible object storage Microsoft Azure Blob storage IBM Cloud Object storage DDN Web object scaler (WOS) SMB/CIFS network share another volume, mounted on the computer as a local volume with Read & Write permissions Users and applications work directly on the source volumes (the online storage tier) and initially all data is created there. Tiger Bridge then applies its data lifecycle management mechanisms to distribute data among the two layers of the virtual unity. Based on user defined policies, Tiger Bridge determines which data should be copied or moved to the target. Optionally, to reduce the amount of duplicated data available on both tiers, Tiger Bridge applies a space reclaiming mechanism, which purges already replicated data from the source volume, leaving just the copies on the target. To achieve this, it takes into consideration the file modification timestamp and other user defined criteria, allowing to discern between stale data and files that are frequently used. To allow users and applications to see and access files having copies only on the target volume, a replicated file is replaced by a stub file. A stub file acts as a placeholder for the actual file on the source volume - it has exactly the same name as the original file, but takes no space and points to the replicated counterpart on the target. Should a user or application attempt to open such a file, Tiger Bridge puts in motion its mechanism for restoring the replica from the target. Once the file is 6

Install and Uninstall Tiger Bridge downloaded to the source volume, it can be easily manipulated if necessary and then re-uploaded automatically using the same replication mechanism. Tiger Bridge tracks and analyzes all changes, schedules the automatic uploads, purges data from the source volume and creates stub files in place of the original files, performing all operations automatically in the background. Both the source and target volumes can contain data, prior to pairing them together. You can pair together more than one source volume with one and the same target. Install and Uninstall Tiger Bridge System Requirements You can install Tiger Bridge on a computer that meets these minimum system requirements: PC with 64-bit (x64) processor. Note: Tiger Bridge actively uses the APIs provided by the target provider (S3, DDN WOS, etc.). These APIs may take significant amount of CPU depending on connection and the amount of data moved. Please, refer to the minimum CPU requirements of your target provider. 64-bit Microsoft Windows 7/Server 2008 R2/Windows 8/Server 2012/Server 2012 R2/ Windows 10/Server 2016. 7

Getting Started with Tiger Bridge 4 GB of physical RAM at least. 30 MB of available hard-disk space for installation. Note: Tiger Bridge keeps track of the files it manages in a database, stored in the product installation folder. The size of the database grows proportionally to the number of files managed. For example, if Tiger Bridge manages 1 000 000 files, the size of the database is approximately 100MB. Unless there s enough free space for the database, Tiger Bridge is unable to operate. TCP ports 8536 and 8537 should not be blocked by a firewall if any. Storage Requirements Source Volume Requirements Tiger Bridge supports any already existing NTFS volume, mounted on the computer running Tiger Bridge as a local volume with Read & Write permissions. Target Storage Requirements S3-compatible object storage IBM Cloud Object Storage Microsoft Azure Blob Storage DDN Web object scaler (WOS) SMB/CIFS network share another volume, mounted on the computer as a local volume with Read & Write permissions Install Tiger Bridge To install Tiger Bridge: 1. Double-click the Tiger Bridge installation file and then click Next. 2. Accept the terms of the software license agreement and click Next. 3. Select the folder where to install Tiger Bridge and click Next. 4. Click Install. 5. When the installation finishes, click Finish. 6. Restart the computer. 8

Uninstall Tiger Bridge Tiger Bridge Interface Important: It is highly recommended to restore all stub files from the target, before uninstalling Tiger Bridge (see Manually Manage Data on page 49). After you uninstall Tiger Bridge you will not be able to restore any stub file from the target volume. To uninstall Tiger Bridge: 1. Display the Control Panel. 2. Double-click Programs and Features. 3. Right-click Tiger Bridge and select Uninstall. 4. When prompted to confirm that you want to remove Tiger Bridge from the computer, click Yes. The uninstallation of Tiger Bridge warns you that you will have to reboot the computer to complete the uninstallation. 5. Click OK. 6. When prompted, restart the computer. Tiger Bridge Interface Once you install Tiger Bridge on the computer, you can use the command-line interface (tiercli) to activate and configure Tiger Bridge and to manually manage data. You can also use the Tiger Bridge shell extension to manually manage data (see Managing Data Through the Shell Extension on page 50). To start the Tiger Bridge s command-line interface, execute the following in command prompt: tiercli Tiger Bridge lists the available commands. To view the command syntax with examples, simply execute a command without providing additional parameters. For example, to view the available commands for setting target, execute the following: tiercli config target For example, to view the correct syntax for setting an S3-compatible object storage as a target, execute the following: tiercli config target s3 9

Getting Started with Tiger Bridge Activate Tiger Bridge Before you activate Tiger Bridge it cannot manage any data on the source volumes and the target. Tiger Bridge makes use of capacity based licenses designating the maximum amount of data Tiger Bridge manages. The capacity is calculated as the sum of the sizes of all files Tiger Bridge manages i.e. the sizes of all already replicated and offline files on the source volumes. Once you reach the capacity for your license, Tiger Bridge will simply stop replicating new files, but can still restore offline files from the target. To activate your Tiger Bridge license: 1. In command prompt, execute the following: tiercli license Tiger Bridge displays the serial number of the product for your computer. Copy the serial number and use it to request the activation key generated for your license. 2. Activate Tiger Bridge, by executing the following: tiercli license [activation key] To view the activation status of Tiger Bridge on your computer: In command prompt, execute the following: tiercli about Tiger Bridge displays the version of the product installed on the computer, the license capacity and until when the license is valid. 10

Configure Tiger Bridge Configuration Parameters............................... 12 Configure Tiger Bridge for Work with S3-compatible Object Storage.. 13 Configure Tiger Bridge for Work with IBM Cloud Object Storage..... 16 Configure Tiger Bridge for Work with Microsoft Azure Blob Storage... 20 Configure Tiger Bridge for Work with DDN Web Object Scaler...... 23 Configure Tiger Bridge for Work with Network Share............. 26 Configure Tiger Bridge for Work with Local Volume Target......... 30 Configure Tiger Bridge to Work in Move Mode................. 32 Change Tiger Bridge Configuration Settings................... 33 Disable Tiger Bridge................................... 34

Configure Tiger Bridge Configuration Parameters To configure Tiger Bridge, you should go through the following steps: Specify the target you must use one and the same target for all your source volumes. Currently Tiger Bridge supports the following targets: S3-compatible object storage IBM cloud object storage Microsoft Azure Blob storage DDN web object scaler (WOS) SMB/CIFS network share another volume, mounted on the computer as a local volume with Read & Write permissions Pair together the source volume(s) with the container on the target each source volume must be paired with a container (a folder on a network share or NTFS volume, a bucket on an S3/DDN WOS storage system) on the selected target. Configure the locations from which data will be replicated create a list of included locations on your source volumes (from which Tiger Bridge will replicate data on the target) and excluded locations (subfolders of the included locations, which are exceptions and whose data will be omitted by Tiger Bridge s data replication and space reclaiming mechanism). Using those two parameters you can specify whether you want to replicate all data on the source volumes, all data except data in specific folders or just data in specific folders. If the locations from which you don t want to replicate data outnumber the locations from which data should be replicated, it will be easier for you to just list all included locations one by one and leave the excluded locations list empty. Vice versa, if the folders on a source volume from which you don t want to replicate data are less than the ones, which should be replicated by Tiger Bridge, you should specify the whole volume as an included location and then list as excluded locations just its subfolders, from which data should not be replicated. Configure the data replication policy for how long a file should not have been modified in order Tiger Bridge to queue it for replication. By default, Tiger Bridge queues for replication data not modified within the last 12 hours. Enable/disable space reclaiming by default, space reclaiming is disabled and replicated data is available on both the source volumes and the target. You can enable/disable space reclaiming at any time. 12

Configure Tiger Bridge for Work with S3-compatible Object Storage Configure space reclaiming policy Tiger Bridge decides which replicated files to replace with stubs on the source volume based on 2 parameters - minimal file size and time interval for which the file has not been accessed. For example, if you set the file size threshold to 10MB and the time interval to 2 weeks, Tiger Bridge will create stub files in the place of replicated files with size 10MB or above that have not been accessed for at least 2 weeks, leaving on the source volume replicated files whose size is smaller than 10MB and also replicated files with bigger size that have been accessed by a client computer in less than 2 weeks. By default, Tiger Bridge replaces files with stubs only if they are bigger than 10MB and if they have not been accessed for more than 100 hours. Specify used space thresholds for space reclaiming by default, space reclaiming is triggered only when used space on the source volumes exceeds 75% of its size. You can also specify maximum used space threshold on your source volumes - it specifies when all files subject to replication are queued for replacement with stub files regardless of their size and last access time. By default, maximum used space value is set to 90% for all source volumes. You can change both of this parameters to match your desired workflow. Note: Tiger Bridge processes the queue of files scheduled for replacement with stubs starting from the ones, which are least recently accessed. Operation mode by default, Tiger Bridge operates in copy mode, which allows duplicated data, available both on the source volumes and the target. To set up the target as a natural extension of your source volume(s) and reduce duplicated content to a minimum, you can set up Tiger Bridge to operate in move mode. When Tiger Bridge operates in move mode, each time a file is restored to the source volume, its copy is deleted from the target. For more details refer to Configure Tiger Bridge to Work in Move Mode on page 32. Configure Tiger Bridge for Work with S3- compatible Object Storage To use Tiger Bridge with S3-compatible object storage as a target, you should: create a separate bucket for each source volume paired with the S3-compatible object storage. provide access key ID and secret access key for access to all buckets designated as containers for each source volume; Important: Do not change the name of the bucket on the S3-compatible object storage as this may prevent Tiger Bridge replication from operating. To configure Tiger Bridge for work with S3-compatible object storage: 1. In command prompt, set s3-compatible object storage as target, by executing the following: tiercli config target s3 <server> <access_id> <secret_key> where: 13

Configure Tiger Bridge <server> is the DNS name or IP address of the s3-compatible object storage server; <access_id> is the Access Key ID used for access to this server; <secret_key> is the Secret Access Key for access to this server; For example, to set as target provider Amazon s web storage service (s3.amazonaws.com), Access Key ID: AKIAI633LOZJPNTZUIBA and Secret Access Key ID: Y2n1rXwda3T9yB7DEE7hRFtC6sMP83jeecwd4LfF, execute the following: tiercli config target s3 s3.amazonaws.com AKIAI633LOZJPNTZUIBA Y2n1rXwda3T9yB7DEE7hRFtC6sMP83jeecwd4LfF 2. Pair the source volume with its container on the target, by executing the following: tiercli config container <drive letter or mount point of the source volume> <name of the bucket on the S3 object storage> For example, to pair source volume Projects mounted as drive letter F:\ to an S3-compatible object storage and replicate data in the bucket named replicas, execute the following: tiercli config container F: replicas Note: If you want to pair other source volumes with the same target, repeat the step above for each new source volume, changing the name of the bucket on the S3 storage. 3. Configure the list of included locations on the source volume(s), from which data will be replicated, by executing one of the following: To add a whole source volume or a folder on a volume to the list of included locations, execute the following: tiercli config include <drive letter or mount point of the source volume> <full path to folder on source volume> Important: You must add all included locations using one command. For the purpose separate each added location with a space. Issuing the command anew will overwrite the previous setting. For example, to add to the list of included locations the root of source volume F: and the folder Data in the root of source volume G:, execute the following: tiercli config include F: G:\Data Tip: In the next step you can then specify which folders (and respectively their subfolders) on the source volume F: should be added as excluded locations i.e. to specify that data from them should not be replicated. To clear the included locations list and start configuring it anew, execute the following: tiercli config include 4. Configure the list of excluded locations on the source volume(s), from which data will not be replicated, by executing one of the following: To add a whole source volume or a folder on a volume to the list of excluded locations, execute the following: 14

Configure Tiger Bridge for Work with S3-compatible Object Storage tiercli config exclude <drive letter or mount point of the source volume> <full path to folder on source volume> Important: You must add all excluded locations using one command. For the purpose separate each added location with a space. Issuing the command anew will overwrite the previous setting. For example, to add as excluded locations the folder Temp in the root of source volume F: and the folder Drafts, which is subfolder of the folder Data in the root of source volume G:, execute the following: tiercli config exclude F:\Temp G:\Data\Drafts To clear the excluded locations list and start configuring it anew, execute the following: tiercli config exclude 5. To set the period for which data must not have been modified in order to be replicated on the target, execute the following: tiercli config policy replicate <period> Where <period> can be the desired period in seconds (s), minutes (m), hours (h), days (d), weeks (w). For example, to specify that Tiger Bridge should replicate data only after it has not been modified for 36 hours, execute the following: tiercli config policy replicate 36h 6. To enable space reclaiming, execute the following: tiercli config policy reclaimspace turn on Note: To disable space reclaiming, execute the following: tiercli config policy reclaimspace turn off 7. To configure for how long a replicated should not have been accessed in order to be replaced by a stub file, execute the following: tiercli config policy reclaimspace age <period> Where <period> can be the desired period in seconds (s), minutes (m), hours (h), days (d), weeks (w). For example. to specify that Tiger Bridge should replace files with stub counterparts only after they have not been accessed for 36 hours, execute the following: tiercli config policy reclaimspace age 36h 15

Configure Tiger Bridge 8. To configure what is the minimal size of a file for it to be replaced by a stub file, execute the following: tiercli config policy reclaimspace size <size> Where <size> is the size in bytes (b), KB (k), MB (m), GB (g), TB (t). For example. to specify that Tiger Bridge should replace files with stub counterparts only if they are bigger than 1GB, execute the following: tiercli config policy reclaimspace size 1g 9. To configure what used space on the source volumes should be reached for Tiger Bridge to trigger space reclaiming, execute the following: tiercli config policy reclaimspace minused <percent> Where <percent> is just the percent value without the % sign. For example, to specify that Tiger Bridge should begin replacing files with stub counterparts once used space on the source volumes reaches 65%, execute the following: tiercli config policy reclaimspace minused 65 10.To configure what used space on the source volumes should be reached for Tiger Bridge to trigger space reclaiming of all replicated files regardless of their size and last access time, execute the following: tiercli config policy reclaimspace maxused <percent> Where <percent> is just the percent value without the % sign. For example, to specify that Tiger Bridge should begin replacing all files with stub counterparts once used space on the source volumes reaches 85%, execute the following: tiercli config policy reclaimspace maxused 85 11.Check if all settings are correctly configured, by executing the following: tiercli config show 12.Reload the updated configuration in the Tiger Bridge service in order to apply all changes, by executing the following: tiercli config reload Configure Tiger Bridge for Work with IBM Cloud Object Storage To use Tiger Bridge with IBM cloud object storage as a target, you should: create a separate bucket for each source volume paired with the IBM cloud object storage. provide access key ID and secret access key for access to all buckets designated as containers for each source volume; 16

Configure Tiger Bridge for Work with IBM Cloud Object Storage Important: Do not change the name of the bucket on the IBM cloud object storage as this may prevent Tiger Bridge replication from operating. To configure Tiger Bridge for work with IBM cloud object storage: 1. In command prompt, set IBM cloud object storage as target, by executing the following: tiercli config target icos <access_id> <secret_key> <main server> [alternative server] [alternative server]... where: <access_id> is the Access Key ID used for access to this server; <secret_key> is the Secret Access Key for access to this server; <main server> is the DNS name or IP address of the main IBM cloud object storage server; [alternative server] is any alternative IP address through which you can access the server providing access to your account for the IBM cloud object storage; Note: You can add as many alternative IP addresses for access to the IBM cloud object storage server, keeping in mind that the main IP address for access to it must be specified first in the command. For example, to set as target an IBM cloud object storage server accessible through main IP address 10.200.4.10 and additional IP address 10.200.4.12, accessible with Access Key ID: AKIAI633LOZJPNTZUIBA and Secret Access Key ID: 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, execute the following: tiercli config target icos AKIAI633LOZJPNTZUIBA Y2n1rXwda3T9yB7DEE7hRFtC6sMP83jeecwd4LfF 10.200.4.10 10.200.4.12 2. Pair the source volume with its container on the target, by executing the following: tiercli config container <drive letter or mount point of the source volume> <name of the bucket on the IBM cloud object storage server> For example, to pair source volume Projects mounted as drive letter F:\ to an IBM cloud object storage server and replicate data in the bucket named replicas, execute the following: tiercli config container F: replicas Note: If you want to pair other source volumes with the same target, repeat the step above for each new source volume, changing the name of the bucket on the S3 storage. 3. Configure the list of included locations on the source volume(s), from which data will be replicated, by executing one of the following: To add a whole source volume or a folder on a volume to the list of included locations, execute the following: tiercli config include <drive letter or mount point of the source volume> <full path to folder on source volume> 17

Configure Tiger Bridge Important: You must add all included locations using one command. For the purpose separate each added location with a space. Issuing the command anew will overwrite the previous setting. For example, to add to the list of included locations the root of source volume F: and the folder Data in the root of source volume G:, execute the following: tiercli config include F: G:\Data Tip: In the next step you can then specify which folders (and respectively their subfolders) on the source volume F: should be added as excluded locations i.e. to specify that data from them should not be replicated. To clear the included locations list and start configuring it anew, execute the following: tiercli config include 4. Configure the list of excluded locations on the source volume(s), from which data will not be replicated, by executing one of the following: To add a whole source volume or a folder on a volume to the list of excluded locations, execute the following: tiercli config exclude <drive letter or mount point of the source volume> <full path to folder on source volume> Important: You must add all excluded locations using one command. For the purpose separate each added location with a space. Issuing the command anew will overwrite the previous setting. For example, to add as excluded locations the folder Temp in the root of source volume F: and the folder Drafts, which is subfolder of the folder Data in the root of source volume G:, execute the following: tiercli config exclude F:\Temp G:\Data\Drafts To clear the excluded locations list and start configuring it anew, execute the following: tiercli config exclude 5. To set the period for which data must not have been modified in order to be replicated on the target, execute the following: tiercli config policy replicate <period> Where <period> can be the desired period in seconds (s), minutes (m), hours (h), days (d), weeks (w). For example, to specify that Tiger Bridge should replicate data only after it has not been modified for 36 hours, execute the following: tiercli config policy replicate 36h 6. To enable space reclaiming, execute the following: tiercli config policy reclaimspace turn on Note: To disable space reclaiming, execute the following: tiercli config policy reclaimspace turn off 18

Configure Tiger Bridge for Work with IBM Cloud Object Storage 7. To configure for how long a replicated should not have been accessed in order to be replaced by a stub file, execute the following: tiercli config policy reclaimspace age <period> Where <period> can be the desired period in seconds (s), minutes (m), hours (h), days (d), weeks (w). For example. to specify that Tiger Bridge should replace files with stub counterparts only after they have not been accessed for 36 hours, execute the following: tiercli config policy reclaimspace age 36h 8. To configure what is the minimal size of a file for it to be replaced by a stub file, execute the following: tiercli config policy reclaimspace size <size> Where <size> is the size in bytes (b), KB (k), MB (m), GB (g), TB (t). For example. to specify that Tiger Bridge should replace files with stub counterparts only if they are bigger than 1GB, execute the following: tiercli config policy reclaimspace size 1g 9. To configure what used space on the source volumes should be reached for Tiger Bridge to trigger space reclaiming, execute the following: tiercli config policy reclaimspace minused <percent> Where <percent> is just the percent value without the % sign. For example, to specify that Tiger Bridge should begin replacing files with stub counterparts once used space on the source volumes reaches 65%, execute the following: tiercli config policy reclaimspace minused 65 10.To configure what used space on the source volumes should be reached for Tiger Bridge to trigger space reclaiming of all replicated files regardless of their size and last access time, execute the following: tiercli config policy reclaimspace maxused <percent> Where <percent> is just the percent value without the % sign. For example, to specify that Tiger Bridge should begin replacing all files with stub counterparts once used space on the source volumes reaches 85%, execute the following: tiercli config policy reclaimspace maxused 85 11.Check if all settings are correctly configured, by executing the following: tiercli config show 12.Reload the updated configuration in the Tiger Bridge service in order to apply all changes, by executing the following: tiercli config reload 19

Configure Tiger Bridge Configure Tiger Bridge for Work with Microsoft Azure Blob Storage To use Microsoft Azure Blob storage as a target, you should: provide the account name and key for access to the Azure Blob storage; create a separate container for each source volume, from which you will replicate data; Important: Do not change the name of the container as this may prevent Tiger Bridge replication from operating. To configure Tiger Bridge for work with Microsoft Azure: 1. In command prompt, set Microsoft Azure as target, by executing the following: tiercli config target azure <account_name> <account_key> <http https> where: <account_name> is the name of your account for the Azure service; <account_key> is the key for your account for the Azure service; <http https> is the protocol type you will use for access to the Azure Blob storage (http or https); For example, to set as target Microsoft Azure Blob storage accessible with storage account rwaccount and account key: OPEkmf7v9ZHZPvNy2HWoxhDZu6QSFw0llCxam+ltoPegcAyw9YoJu8suuA/ QvDPQ4WdbekaTuoDn0wmDwoZ6pg==, and set the protocol type to http, execute the following: tiercli config target azure rwaccount OPEkmf7v9ZHZPvNy2HWoxhDZu6QSFw0llCxam+ltoPegcAyw9YoJu8suuA/ QvDPQ4WdbekaTuoDn0wmDwoZ6pg== http 2. Pair the source volume with its container on the target, by executing the following: tiercli config container <drive letter or mount point of the source volume> <container name> For example, to pair source volume Projects mounted as drive letter F: to a container container1 on the Azure object storage, execute the following: tiercli config container F: container1 Note: If you want to pair other source volumes with the same target, repeat the step above for each new source volume, changing the name of the container on the Azure object storage. 3. Configure the list of included locations on the source volume(s), from which data will be replicated, by executing one of the following: 20

Configure Tiger Bridge for Work with Microsoft Azure Blob Storage To add a whole source volume or a folder on a volume to the list of included locations, execute the following: tiercli config include <drive letter or mount point of the source volume> <full path to folder on source volume> Important: You must add all included locations using one command. For the purpose separate each added location with a space. Issuing the command anew will overwrite the previous setting. For example, to add to the list of included locations the root of source volume F: and the folder Data in the root of source volume G:, execute the following: tiercli config include F: G:\Data Tip: In the next step you can then specify which folders (and respectively their subfolders) on the source volume F: should be added as excluded locations i.e. to specify that data from them should not be replicated. To clear the included locations list and start configuring it anew, execute the following: tiercli config include 4. Configure the list of excluded locations on the source volume(s), from which data will not be replicated, by executing one of the following: To add a whole source volume or a folder on a volume to the list of excluded locations, execute the following: tiercli config exclude <drive letter or mount point of the source volume> <full path to folder on source volume> Important: You must add all excluded locations using one command. For the purpose separate each added location with a space. Issuing the command anew will overwrite the previous setting. For example, to add as excluded locations the folder Temp in the root of source volume F: and the folder Drafts, which is subfolder of the folder Data in the root of source volume G:, execute the following: tiercli config exclude F:\Temp G:\Data\Drafts To clear the excluded locations list and start configuring it anew, execute the following: tiercli config exclude 5. To set the period for which data must not have been modified in order to be replicated on the target, execute the following: tiercli config policy replicate <period> Where <period> can be the desired period in seconds (s), minutes (m), hours (h), days (d), weeks (w). For example, to specify that Tiger Bridge should replicate data only after it has not been modified for 36 hours, execute the following: tiercli config policy replicate 36h 21

Configure Tiger Bridge 6. To enable space reclaiming, execute the following: tiercli config policy reclaimspace turn on Note: To disable space reclaiming, execute the following: tiercli config policy reclaimspace turn off 7. To configure for how long a replicated should not have been accessed in order to be replaced by a stub file, execute the following: tiercli config policy reclaimspace age <period> Where <period> can be the desired period in seconds (s), minutes (m), hours (h), days (d), weeks (w). For example. to specify that Tiger Bridge should replace files with stub counterparts only after they have not been accessed for 36 hours, execute the following: tiercli config policy reclaimspace age 36h 8. To configure what is the minimal size of a file for it to be replaced by a stub file, execute the following: tiercli config policy reclaimspace size <size> Where <size> is the size in bytes (b), KB (k), MB (m), GB (g), TB (t). For example. to specify that Tiger Bridge should replace files with stub counterparts only if they are bigger than 1GB, execute the following: tiercli config policy reclaimspace size 1g 9. To configure what used space on the source volumes should be reached for Tiger Bridge to trigger space reclaiming, execute the following: tiercli config policy reclaimspace minused <percent> Where <percent> is just the percent value without the % sign. For example, to specify that Tiger Bridge should begin replacing files with stub counterparts once used space on the source volumes reaches 65%, execute the following: tiercli config policy reclaimspace minused 65 10.To configure what used space on the source volumes should be reached for Tiger Bridge to trigger space reclaiming of all replicated files regardless of their size and last access time, execute the following: tiercli config policy reclaimspace maxused <percent> Where <percent> is just the percent value without the % sign. For example, to specify that Tiger Bridge should begin replacing all files with stub counterparts once used space on the source volumes reaches 85%, execute the following: tiercli config policy reclaimspace maxused 85 11.Check if all settings are correctly configured, by executing the following: tiercli config show 22

Configure Tiger Bridge for Work with DDN Web Object Scaler 12.Reload the updated configuration in the Tiger Bridge service in order to apply all changes, by executing the following: tiercli config reload Configure Tiger Bridge for Work with DDN Web Object Scaler To use Tiger Bridge with a DDN WOS appliance as a target, you should: provide the user name and password of an account that has Read & Write permissions to the DDN WOS appliance; create a separate policy for each source volume paired with the DDN WOS appliance. Each policy should meet the following requirements: the policy is not used for another source volume; each policy is searchable; the Search field of each policy must contain the following values: TT_ID TT_PARENT_ID Important: Do not change the name of the policy on the DDN WOS appliance as this may prevent Tiger Bridge replication from operating. To configure Tiger Bridge for work with DDN WOS appliance: 1. In command prompt, set a DDN WOS as target, by executing the following: tiercli config target wos <server_url> <username> <password> where: <server_url> is the address (URL) of the DDN WOS appliance; <username> is the name of the account that has Read & Write permissions to the DDN WOS appliance; <password> is the password of the account that has Read & Write permissions to the DDN WOS appliance; For example, to set as target provider a DDN WOS appliance with URL 10.200.9.5, account name: rwaccount and account password: rwaccountpassword, execute the following: tiercli config target wos 10.200.9.5 rwaccount rwaccountpassword 23

Configure Tiger Bridge 2. Pair the source volume with its container on the target, by executing the following: tiercli config container <drive letter or mount point of the source volume> <name of the bucket on the wos appliance> For example, to pair source volume Projects mounted as drive letter F: to a DDN WOS appliance and replicate data in the bucket named bucket1, execute the following: tiercli config container F: bucket1 Note: If you want to pair other source volumes with the same target, repeat the step above for each new source volume, changing the name of the bucket on the DDN WOS appliance. 3. Configure the list of included locations on the source volume(s), from which data will be replicated, by executing one of the following: To add a whole source volume or a folder on a volume to the list of included locations, execute the following: tiercli config include <drive letter or mount point of the source volume> <full path to folder on source volume> Important: You must add all included locations using one command. For the purpose separate each added location with a space. Issuing the command anew will overwrite the previous setting. For example, to add to the list of included locations the root of source volume F: and the folder Data in the root of source volume G:, execute the following: tiercli config include F: G:\Data Tip: In the next step you can then specify which folders (and respectively their subfolders) on the source volume F: should be added as excluded locations i.e. to specify that data from them should not be replicated. To clear the included locations list and start configuring it anew, execute the following: tiercli config include 4. Configure the list of excluded locations on the source volume(s), from which data will not be replicated, by executing one of the following: To add a whole source volume or a folder on a volume to the list of excluded locations, execute the following: tiercli config exclude <drive letter or mount point of the source volume> <full path to folder on source volume> Important: You must add all excluded locations using one command. For the purpose separate each added location with a space. Issuing the command anew will overwrite the previous setting. For example, to add as excluded locations the folder Temp in the root of source volume F: and the folder Drafts, which is subfolder of the folder Data in the root of source volume G:, execute the following: tiercli config exclude F:\Temp G:\Data\Drafts 24

Configure Tiger Bridge for Work with DDN Web Object Scaler To clear the excluded locations list and start configuring it anew, execute the following: tiercli config exclude 5. To set the period for which data must not have been modified in order to be replicated on the target, execute the following: tiercli config policy replicate <period> Where <period> can be the desired period in seconds (s), minutes (m), hours (h), days (d), weeks (w). For example, to specify that Tiger Bridge should replicate data only after it has not been modified for 36 hours, execute the following: tiercli config policy replicate 36h 6. To enable space reclaiming, execute the following: tiercli config policy reclaimspace turn on Note: To disable space reclaiming, execute the following: tiercli config policy reclaimspace turn off 7. To configure for how long a replicated should not have been accessed in order to be replaced by a stub file, execute the following: tiercli config policy reclaimspace age <period> Where <period> can be the desired period in seconds (s), minutes (m), hours (h), days (d), weeks (w). For example. to specify that Tiger Bridge should replace files with stub counterparts only after they have not been accessed for 36 hours, execute the following: tiercli config policy reclaimspace age 36h 8. To configure what is the minimal size of a file for it to be replaced by a stub file, execute the following: tiercli config policy reclaimspace size <size> Where <size> is the size in bytes (b), KB (k), MB (m), GB (g), TB (t). For example. to specify that Tiger Bridge should replace files with stub counterparts only if they are bigger than 1GB, execute the following: tiercli config policy reclaimspace size 1g 9. To configure what used space on the source volumes should be reached for Tiger Bridge to trigger space reclaiming, execute the following: tiercli config policy reclaimspace minused <percent> Where <percent> is just the percent value without the % sign. For example, to specify that Tiger Bridge should begin replacing files with stub counterparts once used space on the source volumes reaches 65%, execute the following: tiercli config policy reclaimspace minused 65 25

Configure Tiger Bridge 10.To configure what used space on the source volumes should be reached for Tiger Bridge to trigger space reclaiming of all replicated files regardless of their size and last access time, execute the following: tiercli config policy reclaimspace maxused <percent> Where <percent> is just the percent value without the % sign. For example, to specify that Tiger Bridge should begin replacing all files with stub counterparts once used space on the source volumes reaches 85%, execute the following: tiercli config policy reclaimspace maxused 85 11.Check if all settings are correctly configured, by executing the following: tiercli config show 12.Reload the updated configuration in the Tiger Bridge service in order to apply all changes, by executing the following: tiercli config reload Configure Tiger Bridge for Work with Network Share Currently, Tiger Bridge bridge supports SMB/CIFS network shares as target. To set a network share as a target, you should: provide the user name and password of an account that has Read & Write permissions to the network share; create a separate folder on the network share for each source volume paired with the target. All folders designated for storing replicated data from different source volumes must be at the same level in the folder structure of the network share. For example, if you intend to replicate data from 3 source volumes (D:\, E:\ and F:\) and you want to replicate their data in the folder Replication in the root of the network share mounted as \\server\share, the paths to the separate folders for each source volume must be as follows: \\server\share\replication\d \\server\share\replication\e \\server\share\replication\f In the example above, creating a folder F mounted in the root of the share (\\server\share\f) will not be a valid replication location. Important: Once you create the folders, do not change their names as this may prevent Tiger Bridge replication from operating. 26

To configure Tiger Bridge for work with a network share: Configure Tiger Bridge for Work with Network Share 1. In command prompt, set a network share as target, by executing the following: tiercli config target network <sharepath> <username> <password> where: <sharepath> is the full path to folder containing the subfolders for each source volume on the SMB/CIFS network share; <username> is the name of the account that has Read & Write permissions to the network share; <password> is the password of the account that has Read & Write permissions to the network share; For example, to set as target provider a SMB/CIFS network share accessible as \\server\share and the separate folders for each source volume are created in the subfolder Replication in the root of the share, and you will use the following credentials for access to the share account name: rwaccount and account password: rwaccountpassword, execute the following: tiercli config target network \\server\share\replication rwaccount rwaccountpassword Important: The path to the folder on the share must be provided without a final backslash. Important: If the account for access to the network share is an Active Directory domain account, you must specify it with its full domain name. For example, user@domain.com. 2. Pair the source volume with its designated container on the network share, by executing the following: tiercli config container <drive letter or mount point of the source volume> <name of the folder on the network share> For example, to pair source volume Projects mounted as drive letter F: to a network share and replicate data in the folder backup on the network share, execute the following: tiercli config container F: backup Note: If you want to pair other source volumes with the same target, repeat the step above for each new source volume, changing the name of the folder on the network share. 3. Configure the list of included locations on the source volume(s), from which data will be replicated, by executing one of the following: To add a whole source volume or a folder on a volume to the list of included locations, execute the following: tiercli config include <drive letter or mount point of the source volume> <full path to folder on source volume> 27

Configure Tiger Bridge for Work with Network Share 7. To configure for how long a replicated should not have been accessed in order to be replaced by a stub file, execute the following: tiercli config policy reclaimspace age <period> Where <period> can be the desired period in seconds (s), minutes (m), hours (h), days (d), weeks (w). For example. to specify that Tiger Bridge should replace files with stub counterparts only after they have not been accessed for 36 hours, execute the following: tiercli config policy reclaimspace age 36h 8. To configure what is the minimal size of a file for it to be replaced by a stub file, execute the following: tiercli config policy reclaimspace size <size> Where <size> is the size in bytes (b), KB (k), MB (m), GB (g), TB (t). For example. to specify that Tiger Bridge should replace files with stub counterparts only if they are bigger than 1GB, execute the following: tiercli config policy reclaimspace size 1g 9. To configure what used space on the source volumes should be reached for Tiger Bridge to trigger space reclaiming, execute the following: tiercli config policy reclaimspace minused <percent> Where <percent> is just the percent value without the % sign. For example, to specify that Tiger Bridge should begin replacing files with stub counterparts once used space on the source volumes reaches 65%, execute the following: tiercli config policy reclaimspace minused 65 10.To configure what used space on the source volumes should be reached for Tiger Bridge to trigger space reclaiming of all replicated files regardless of their size and last access time, execute the following: tiercli config policy reclaimspace maxused <percent> Where <percent> is just the percent value without the % sign. For example, to specify that Tiger Bridge should begin replacing all files with stub counterparts once used space on the source volumes reaches 85%, execute the following: tiercli config policy reclaimspace maxused 85 11.Check if all settings are correctly configured, by executing the following: tiercli config show 12.Reload the updated configuration in the Tiger Bridge service in order to apply all changes, by executing the following: tiercli config reload 29

Configure Tiger Bridge Configure Tiger Bridge for Work with Local Volume Target To use another local volume as a target for data replication and space reclaiming, you should: make sure that the volume is mounted as a local volume with Read & Write permissions on the computer; create a separate folder on the volume for each source volume paired with the target. To configure Tiger Bridge for work with a local volume: 1. In command prompt, set a local volume as target, by executing the following: tiercli config target local 2. Pair the source volume with its designated container on the target volume, by executing the following: tiercli config container <drive letter or mount point of the source volume> <full path to the folder on the target> For example, to pair source volume Projects mounted as drive letter F: with the folder Projects in the root of the NTFS volume mounted as drive letter G:, execute the following: tiercli config container F: G:\Projects Note: If you want to pair other source volumes with the same target, repeat the step above for each new source volume, changing the name of the folder on the target volume. 3. Configure the list of included locations on the source volume(s), from which data will be replicated, by executing one of the following: To add a whole source volume or a folder on a volume to the list of included locations, execute the following: tiercli config include <drive letter or mount point of the source volume> <full path to folder on source volume> Important: You must add all included locations using one command. For the purpose separate each added location with a space. Issuing the command anew will overwrite the previous setting. For example, to add to the list of included locations the root of source volume F: and the folder Data in the root of source volume G:, execute the following: tiercli config include F: G:\Data Tip: In the next step you can then specify which folders (and respectively their subfolders) on the source volume F: should be added as excluded locations i.e. to specify that data from them should not be replicated. To clear the included locations list and start configuring it anew, execute the following: tiercli config include 30

Configure Tiger Bridge for Work with Local Volume Target 4. Configure the list of excluded locations on the source volume(s), from which data will not be replicated, by executing one of the following: To add a whole source volume or a folder on a volume to the list of excluded locations, execute the following: tiercli config exclude <drive letter or mount point of the source volume> <full path to folder on source volume> Important: You must add all excluded locations using one command. For the purpose separate each added location with a space. Issuing the command anew will overwrite the previous setting. For example, to add as excluded locations the folder Temp in the root of source volume F: and the folder Drafts, which is subfolder of the folder Data in the root of source volume G:, execute the following: tiercli config exclude F:\Temp G:\Data\Drafts To clear the excluded locations list and start configuring it anew, execute the following: tiercli config exclude 5. To set the period for which data must not have been modified in order to be replicated on the target, execute the following: tiercli config policy replicate <period> Where <period> can be the desired period in seconds (s), minutes (m), hours (h), days (d), weeks (w). For example, to specify that Tiger Bridge should replicate data only after it has not been modified for 36 hours, execute the following: tiercli config policy replicate 36h 6. To enable space reclaiming, execute the following: tiercli config policy reclaimspace turn on Note: To disable space reclaiming, execute the following: tiercli config policy reclaimspace turn off 7. To configure for how long a replicated should not have been accessed in order to be replaced by a stub file, execute the following: tiercli config policy reclaimspace age <period> Where <period> can be the desired period in seconds (s), minutes (m), hours (h), days (d), weeks (w). For example. to specify that Tiger Bridge should replace files with stub counterparts only after they have not been accessed for 36 hours, execute the following: tiercli config policy reclaimspace age 36h 31

Configure Tiger Bridge 8. To configure what is the minimal size of a file for it to be replaced by a stub file, execute the following: tiercli config policy reclaimspace size <size> Where <size> is the size in bytes (b), KB (k), MB (m), GB (g), TB (t). For example. to specify that Tiger Bridge should replace files with stub counterparts only if they are bigger than 1GB, execute the following: tiercli config policy reclaimspace size 1g 9. To configure what used space on the source volumes should be reached for Tiger Bridge to trigger space reclaiming, execute the following: tiercli config policy reclaimspace minused <percent> Where <percent> is just the percent value without the % sign. For example, to specify that Tiger Bridge should begin replacing files with stub counterparts once used space on the source volumes reaches 65%, execute the following: tiercli config policy reclaimspace minused 65 10.To configure what used space on the source volumes should be reached for Tiger Bridge to trigger space reclaiming of all replicated files regardless of their size and last access time, execute the following: tiercli config policy reclaimspace maxused <percent> Where <percent> is just the percent value without the % sign. For example, to specify that Tiger Bridge should begin replacing all files with stub counterparts once used space on the source volumes reaches 85%, execute the following: tiercli config policy reclaimspace maxused 85 11.Check if all settings are correctly configured, by executing the following: tiercli config show 12.Reload the updated configuration in the Tiger Bridge service in order to apply all changes, by executing the following: tiercli config reload Configure Tiger Bridge to Work in Move Mode By default, Tiger Bridge operates in copy mode, in which the target acts as a safety net for recovering data to the source volume. The normal workflow in copy mode allows duplicated content on the two tiers, even when space reclaiming is enabled. When you want the target to operate as a natural extension of your source volumes, meaning that a file instance exists solely on one or the other tier of the unit, but not on both at the same time, you should configure Tiger Bridge to operate in move mode. With this in mind, Tiger Bridge s move 32

Change Tiger Bridge Configuration Settings mode attempts to reduce duplicated content to a minimum. Thus, the main difference with copy mode is that when you restore a stub file, its copy on the target is not kept in order to provide more free space. In contrast, in copy mode to delete a file from the target, you must delete it from your source volume too. In move mode, until you redefine the parameters for space reclaiming, replicated data may be available on both the source volume(s) and the target. You can cope with such data duplication by redefining the parameters for data replication and space reclaiming in such a way that the decisive factor whether a file should be stored on the source volume or on the target is only the used space size on the source volume. The sample settings below configure Tiger Bridge to automatically move (replicate and replace with a stub counterpart) to the target any file regardless of its size and last access time, starting from the ones, which are least recently modified, once used space on the source volume reaches 70%: tiercli config policy replicate 200000w tiercli config policy reclaimspace turn on tiercli config policy reclaimspace age 200000w tiercli config policy reclaimspace size 0 tiercli config policy reclaimspace minused 65 tiercli config policy reclaimspace maxused 70 tiercli config policy reclaimspace mode move tiercli config reload Change Tiger Bridge Configuration Settings While you can change the target at any time, you should keep in mind that this might result in data loss as all already replicated files will be inaccessible from the new replication target and you will not be able to restore them using Tiger Bridge. Should you decide to change any of the data replication and space reclaiming settings of your current configuration, you should simply execute the desired command from the configuration steps with the new parameters and then reload the configuration to apply the changes. The settings you might consider changing after you have configured Tiger Bridge for work with the respective target include: included and excluded locations from which data will be replicated. the time for which a file has not been modified in order Tiger Bridge to replicate it. enable/disable space reclaiming. 33

Configure Tiger Bridge minimum size of files, which should be replaced by stub files on the source volumes i.e. specifying that files below this size should not be replaced by stub files. last access time of files as a marker of stale data i.e. specifying less frequently accessed files, which should be replaced by stub on the source volumes. minimum used space on source volumes, which after exceeded triggers space reclaiming of files matching your space reclaiming criteria. maximum used space on source volumes, which after exceeded triggers space reclaiming of all files regardless of their size and last access time. Disable Tiger Bridge You can disable Tiger Bridge at any time without uninstalling it. Keep in mind that once you disable Tiger Bridge, you will not be able to restore any stub files from the target either on demand or manually. To disable Tiger Bridge: In command prompt, execute the following: tiercli config disable 34

Manage Advanced Settings Minimum File Size for Replication...................... 37 File Restore Behaviour............................. 38 Specify the Processes Triggering File Restore.............. 38 Partial File Restore Behaviour......................... 40 Enable/Disable Write-through on File Restore............. 40 Set File Restore Timeout............................ 41 Set Stub File Allocation Size Display Option............... 42 Set Stub File Head and Tail Sizes...................... 42 Set Startup Scan Wait Time.......................... 43 Set Number of Parallel Threads during Data Replication...... 44 Manage Tiger Bridge Logs........................... 44

Manage Advanced Settings To let you fine-tune your workflow with Tiger Bridge, you can change the following advanced settings: change the default behaviour when a file is deleted from a source volume (see Delete File Behaviour on page 36). specify the minimum size of a file for it to be replicated (see Minimum File Size for Replication on page 37). specify whether a file should be restored each time a user or application attempts to open it (default behaviour) or only when you manually restore it through Tiger Bridge (see File Restore Behaviour on page 38). create a list of processes allowed to trigger automatic restoring of files from the target (see Specify the Processes Triggering File Restore on page 38). specify whether an application can begin reading a file before it has been fully restored (see Partial File Restore Behaviour on page 40). specify whether to turn on/off write-through restore of files (see Enable/Disable Write-through on File Restore on page 40). specify timeout after which a file restore operation should be considered unsuccessful (see Set File Restore Timeout on page 41). specify whether Tiger Bridge should show the actual size of a stub file or the size of the replicated file it replaces (see Set Stub File Allocation Size Display Option on page 42). specify stub file head and tail size (see Set Stub File Head and Tail Sizes on page 42). specify for how long Tiger Bridge should wait on startup for the file system scan before beginning to perform data replication and space reclaiming (see Set Startup Scan Wait Time on page 43). specify the number of parallel threads run by Tiger Bridge when replicating files to the target (see Set Number of Parallel Threads during Data Replication on page 44). manage Tiger Bridge logs (see Manage Tiger Bridge Logs on page 44). Delete File Behaviour By default, when a file is deleted from the source volume, its replica is automatically deleted from the target as well. You can change this default behaviour and set Tiger Bridge to delete just the instance of the file on the source volume. To restore the replica from the target, you will have to synchronize the contents of the source volume and the target (see Synchronize Data on the Source Volume and the Target on page 53). 36

To specify file delete behaviour on the target: 1. Start the Registry Editor. Minimum File Size for Replication Tip: To start Registry Editor, on the Start menu click Run and in the dialog type regedit. 2. Navigate to: HKEY_LOCAL_MACHINE\SOFTWARE\Tiger Technology\tiger-bridge\tiersvc\settings 3. Right-click in the right pane and select New String Value. 4. Rename the new REG_SZ value to: delete-file-replica 5. Right-click the delete-file-replica value and select Modify. 6. Do one of the following: to set Tiger Bridge to keep the replica on the target after the file has been deleted on the source volume, change the value to 0 and click OK. to set Tiger Bridge to delete the file both from the source volume and the target, change the value to 1 and click OK. 7. Restart the computer running Tiger Bridge. Minimum File Size for Replication By default, the only criteria for queuing a file for replication is for how long this file have not been modified. You can also set Tiger Bridge to queue for replication only files whose size is above a given threshold, thus ignoring small files like log files, for example. Note: The minimum file size for replication setting is valid only for files scheduled for automatic replication. Should you manually replicate a file with size below this minimum, this file will be replicated. To specify minimum file size for it to be replicated: 1. Start the Registry Editor. Tip: To start Registry Editor, on the Start menu click Run and in the dialog type regedit. 2. Navigate to: HKEY_LOCAL_MACHINE\SOFTWARE\Tiger Technology\tiger-bridge\tiersvc\settings 3. Right-click the replicate-filesize value and select Modify. 4. Do one of the following: to set Tiger Bridge to replicate any file regardless of its size, change the value to 0 and click OK. 37

Manage Advanced Settings to set Tiger Bridge to schedule for automatic replication only files with size above the one you specify, enter the minimum file size in bytes and click OK. For example, to set Tiger Bridge to replicate only files whose size is above 100MB, enter 104857600 and click OK. 5. Restart the computer running Tiger Bridge. File Restore Behaviour By default, Tiger Bridge is set up to automatically restore a stub file from the target each time a user or application accesses it. You can change this default behaviour and specify that stub files should be restored from the target only when a manual restore operation is executed through the command-line interface or the shell extension of Tiger Bridge. To specify file restore behaviour: 1. Start the Registry Editor. Tip: To start Registry Editor, on the Start menu click Run and in the dialog type regedit. 2. Navigate to: HKEY_LOCAL_MACHINE\SOFTWARE\Tiger Technology\tiger-bridge\tiersvc\settings 3. Right-click the Enable active restore string value and select Modify. 4. Do one of the following: to set Tiger Bridge to automatically restore a stub file, when a user or application accesses it, change the value to 1 and click OK. to set Tiger Bridge to restore a stub file, only if manual restore operation is executed from the command-line interface or the shell extension, change the value to 0 and click OK. 5. Restart the computer running Tiger Bridge. Specify the Processes Triggering File Restore By default, each process attempting to open a stub file on the source volume triggers its restoring from the target. To prevent useless restoring of stub files by your antivirus software, for example, Tiger Bridge allows you to specify which processes exactly can trigger the file restore operation. You can do this by creating either a list of processes allowed to trigger restoring or by creating a list of processes, which cannot trigger restoring of stub files. There is no need to create both lists. In case you create a list of processes allowed to trigger restoring, any process not included in the list will not trigger the restoring of a stub file, when this process attempts to open the file. In case you decide 38

Specify the Processes Triggering File Restore to specify the processes, which are not allowed to trigger restoring, any process outside the list will trigger the restoring of a stub file, when this process attempts to open the file. To specify the processes allowed to trigger stub file restoring: 1. Start the Registry Editor. Tip: To start Registry Editor, on the Start menu click Run and in the dialog type regedit. 2. Navigate to: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\tierflt 3. Right-click in the right pane and select New String Value. 4. Rename the new REG_SZ value to: WhiteProcessList 5. Right-click the WhiteProcessList string value and select Modify. 6. Do one of the following: to add a process to the list, enter its name (for example, explorer.exe) and click OK. Note: To add more than one process, separate each process name with space. to remove a process from the list, delete its name from the list and click OK. 7. Restart the computer running Tiger Bridge. To specify the processes forbidden to trigger stub file restoring: 1. Start the Registry Editor. Tip: To start Registry Editor, on the Start menu click Run and in the dialog type regedit. 2. Navigate to: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\tierflt 3. Right-click in the right pane and select New String Value. 4. Rename the new REG_SZ value to: BlackProcessList 5. Right-click the BlackProcessList string value and select Modify. 6. Do one of the following: to add a process to the list, enter its name (for example, explorer.exe) and click OK. Note: To add more than one process, separate each process name with space. to remove a process from the list, delete its name from the list and click OK. 7. Restart the computer running Tiger Bridge. 39

Manage Advanced Settings Partial File Restore Behaviour By default, when Tiger Bridge restores a stub file from the target, an application can begin reading it only after it has been fully restored on the source volume. With network share or another local volume as targets, you can begin reading a file before it is fully restored. To achieve this, you must change the default partial file restore behaviour. To specify partial file restore behaviour: 1. Start the Registry Editor. Tip: To start Registry Editor, on the Start menu click Run and in the dialog type regedit. 2. Navigate to: HKEY_LOCAL_MACHINE\SOFTWARE\Tiger Technology\tiger-bridge\tiersvc\settings 3. Right-click the enable-partial-restore string value and select Modify. 4. Do one of the following: to set Tiger Bridge to allow reading a stub file, only when it has been fully restored, change the value to 0 and click OK. to set Tiger Bridge to allow reading a stub file, when just a part of it has been restored only, change the value to 1 and click OK. Important: Allowing reading of stub files when they have been only partially restored is not suitable for s3 storage and wos appliances as targets. 5. Restart the computer running Tiger Bridge. Enable/Disable Write-through on File Restore By default, when a file is being restored, write-through is disabled. To specify that write operations should not go through any intermediate cache, but go directly to the disk of the source volume, you should enable write-through. Important: It is advisable to enable write-through on file restore, only when your source volume is accessible in SAN environment. To enable/disable write-through on file restore: 1. Start the Registry Editor. Tip: To start Registry Editor, on the Start menu click Run and in the dialog type regedit. 2. Navigate to: HKEY_LOCAL_MACHINE\SOFTWARE\Tiger Technology\tiger-bridge\tiersvc\settings 3. Right-click the enable-write-through-restore value and select Modify. 40

4. Do one of the following: Set File Restore Timeout to let Tiger Bridge buffer data when restoring a file, change the value to 0 and click OK. to let Tiger Bridge restore data unbuffered to the source volume, change the value to 1 and click OK. 5. Restart the computer running Tiger Bridge. Set File Restore Timeout By default, when attempting to restore a file from the target Tiger Bridge waits 60 seconds for the operation to begin before returning error for unsuccessful operation. You can change this default timeout adjusting it to the particular target you are using and the connection to it. Additionally, you can specify a timeout for successfully restoring a file, which is calculated as milliseconds for each 1MB of the file size. By default, the value is set to 1000 milliseconds. To set file restore started successfully timeout: 1. Start the Registry Editor. Tip: To start Registry Editor, on the Start menu click Run and in the dialog type regedit. 2. Navigate to: HKEY_LOCAL_MACHINE\SOFTWARE\Tiger Technology\tiger-bridge\tiersvc\settings 3. Right-click the Active restore timeout value and select Modify. 4. Enter the timeout value in seconds and click OK. For example, to set Tiger Bridge to return error for unsuccessful restore of a file after 2 minutes, enter 120 and click OK. 5. Restart the computer running Tiger Bridge. To set successful file restore timeout: 1. Start the Registry Editor. Tip: To start Registry Editor, on the Start menu click Run and in the dialog type regedit. 2. Navigate to: HKEY_LOCAL_MACHINE\SOFTWARE\Tiger Technology\tiger-bridge\tiersvc\settings 3. Right-click the active-restore-bandwidth value and select Modify. 4. Enter the timeout value in milliseconds per 1MB of the total file size and click OK. For example, to set Tiger Bridge to return error for unsuccessful restore of a file if it is unable to restore 1MB of the file for 2 minutes, enter 120000 and click OK. 41

Manage Advanced Settings 5. Restart the computer running Tiger Bridge. Set Stub File Allocation Size Display Option By default, when you request to view the actual size of a stub file on the source volume, Tiger Bridge displays the actual size of the original file it has replaced. You can set Tiger Bridge to display the actual size of the stub file instead, keeping in mind that using this option may disturb the workflow of some applications. To set stub file allocation size display option: 1. Start the Registry Editor. Tip: To start Registry Editor, on the Start menu click Run and in the dialog type regedit. 2. Navigate to: HKEY_LOCAL_MACHINE\SOFTWARE\Tiger Technology\tiger-bridge\tiersvc\settings 3. Right-click the show-actual-size value and select Modify. 4. Do one of the following: to set Tiger Bridge to display the allocation size of the original file instead of the actual size of the stub file, change the value to 0 and click OK. to set Tiger Bridge to display the actual size of the stub file, change the value to 1 and click OK. 5. Restart the computer running Tiger Bridge. Set Stub File Head and Tail Sizes By default, stub files keep none of the original file s data or metadata and take no space on the source volume. Because of this it is possible a stub file to be restored from the target simply because Windows Explorer, for example, attempts to read the supplemental data placed in the header of a file (with some file types this information may also be stored in the end of a file). To prevent needless restoring of stub files, you can set Tiger Bridge to keep the beginning and/or the end of stub files, specifying the size of respectively the head and the tail of the file. Thus, if the specified size is enough to hold the information from the header of a file, upon requesting to read it Windows Explorer will not trigger restoring the original file from the target. With most file types a head/tail size of 64KB would be sufficient to include the information from the file header. Keep in mind that by specifying head and/or tail size, you automatically increase the size of each stub file on your source volume with the sum of the head/tail sizes. 42

To set stub file head size: 1. Start the Registry Editor. Set Startup Scan Wait Time Tip: To start Registry Editor, on the Start menu click Run and in the dialog type regedit. 2. Navigate to: HKEY_LOCAL_MACHINE\SOFTWARE\Tiger Technology\tiger-bridge\tiersvc\settings 3. Right-click the stub-sparse-head-size value and select Modify. 4. Enter the size of the head of each stub file to be kept on the source volume and click OK. 5. Restart the computer running Tiger Bridge. To set stub file tail size: 1. Start the Registry Editor. Tip: To start Registry Editor, on the Start menu click Run and in the dialog type regedit. 2. Navigate to: HKEY_LOCAL_MACHINE\SOFTWARE\Tiger Technology\tiger-bridge\tiersvc\settings 3. Right-click the stub-sparse-tail-size value and select Modify. 4. Enter the size of the tail of each stub file to be kept on the source volume and click OK. 5. Restart the computer running Tiger Bridge. Set Startup Scan Wait Time On startup Tiger Bridge scans the file systems of the source volumes it manages to determine what data on them needs to be processed. By default, Tiger Bridge is set to wait until this scan finishes, before beginning with data replication and space reclaiming, thus ensuring maximum precision of the scheduled file operations. On source volumes with much data this scan may take significant time and you can set up Tiger Bridge to reduce this wait time before the scan finishes. To set Tiger Bridge startup scan wait time: 1. Start the Registry Editor. Tip: To start Registry Editor, on the Start menu click Run and in the dialog type regedit. 2. Navigate to: HKEY_LOCAL_MACHINE\SOFTWARE\Tiger Technology\tiger-bridge\tiersvc\settings 3. Right-click in the right pane and select New String Value. 4. Rename the new REG_SZ value to: step-ready-wait time 43

Manage Advanced Settings 5. Right-click the step-ready-wait time value and select Modify. 6. Do one of the following: to set Tiger Bridge to wait until the startup scan finishes completely, change the value to 0 and click OK. enter the time in seconds, for which Tiger Bridge should wait before beginning to process data and click OK. 7. Restart the computer running Tiger Bridge. Set Number of Parallel Threads during Data Replication By default, when Tiger Bridge replicates files to the target, it runs just one thread. You can increase the number of threads for remote targets, like IBM cloud object storage for example. To set the number of parallel threads during data replication: 1. Start the Registry Editor. Tip: To start Registry Editor, on the Start menu click Run and in the dialog type regedit. 2. Navigate to: HKEY_LOCAL_MACHINE\SOFTWARE\Tiger Technology\tiger-bridge\tiersvc\settings 3. Right-click the step-thread-cnt time value and select Modify. 4. Enter the number of threads that Tiger Bridge should use when replicating data to the target and click OK. 5. Restart the computer running Tiger Bridge. Manage Tiger Bridge Logs Tiger Bridge can log most events related to its operations, using a standard Windows output console like DebugView, for example. You can set Tiger Bridge to output its logs as files in a selected directory or in the Windows Event Viewer. Important: You should keep track of the amount of log files generated by Tiger Bridge to avoid running out of disk space. You can also set Tiger Bridge to create logs for the following events: a file is replicated a file is replaced with a stub file 44

a stub file is restored from the target Manage Tiger Bridge Logs the status of a directory is changed (replicated, offline) To change the output of the Tiger Bridge logs: 1. Start the Registry Editor. Tip: To start Registry Editor, on the Start menu click Run and in the dialog type regedit. 2. Navigate to: HKEY_LOCAL_MACHINE\SOFTWARE\Tiger Technology\tiger-bridge\tiersvc\settings 3. Right-click the tiersvc key and select New Key. 4. Rename the new key to log. 5. Right-click in the right pane and select New String Value. 6. Rename the new REG_SZ value to: user_destination 7. Right-click the user_destination value and select Modify. 8. Do one of the following: To enable Tiger Bridge logging to a file in a selected directory, enter the following and then click OK: file://[full path to the directory]\ For example, to set Tiger Bridge to create the log files in the Logs directory in the root of your system drive C:, enter the following: file://c:\logs\ Note: The directory you specify must exist. The backslash at the end of the path is obligatory. To enable Tiger Bridge in the Windows Event Viewer, enter the following and then click OK: eventlog:[logging source name] For example, to set the Tiger Bridge logs in the Event Viewer to appear with source TigerBridge, enter the following: eventlog:tigerbridge 9. Restart the computer running Tiger Bridge. Note: To disable logging to a file or in Event Viewer, simply delete the user_destination registry value. To enable/disable Tiger Bridge logging on each file replicate operation: 1. Start the Registry Editor. Tip: To start Registry Editor, on the Start menu click Run and in the dialog type regedit. 45

Manage Advanced Settings 2. Navigate to: HKEY_LOCAL_MACHINE\SOFTWARE\Tiger Technology\tiger-bridge\tiersvc\settings 3. Right-click the enable-replicate-log value and select Modify. 4. Do one of the following: To enable Tiger Bridge logging, change the value to 1 and click OK. To disable Tiger Bridge logging, change the value to 0 and click OK. 5. Restart the computer running Tiger Bridge. To enable/disable Tiger Bridge logging on replace with a stub file operation: 1. Start the Registry Editor. Tip: To start Registry Editor, on the Start menu click Run and in the dialog type regedit. 2. Right-click the enable-offline-log value and select Modify. 3. Do one of the following: To enable Tiger Bridge logging, change the value to 1 and click OK. To disable Tiger Bridge logging, change the value to 0 and click OK. 4. Restart the computer running Tiger Bridge. To enable/disable Tiger Bridge logging on file restore operation: 1. Start the Registry Editor. Tip: To start Registry Editor, on the Start menu click Run and in the dialog type regedit. 2. Right-click the enable-restore-log value and select Modify. 3. Do one of the following: To enable Tiger Bridge logging, change the value to 1 and click OK. To disable Tiger Bridge logging, change the value to 0 and click OK. 4. Restart the computer running Tiger Bridge. To enable/disable Tiger Bridge logging on directory status change: 1. Start the Registry Editor. Tip: To start Registry Editor, on the Start menu click Run and in the dialog type regedit. 2. Right-click the enable-dir-status-log value and select Modify. 3. Do one of the following: To enable Tiger Bridge logging, change the value to 1 and click OK. 46

To disable Tiger Bridge logging, change the value to 0 and click OK. 4. Restart the computer running Tiger Bridge. Manage Tiger Bridge Logs 47

48 Manage Advanced Settings

Manually Manage Data Managing Data Through the Shell Extension.............. 50 Managing Data Through the Command-line Interface........ 52 Synchronize Data on the Source Volume and the Target...... 53

Manually Manage Data Using Tiger Bridge s shell extension or command-line interface you can manually replicate files (or whole folders), create stub files or restore files from the target. Initiating a Tiger Bridge operation manually always takes precedence over the automatically scheduled tasks. That means that if you choose to manually replicate files through the shell extension or the command-line interface, the execution of the operation will begin immediately and will pause the automatic replication queue that is being processed at the moment. Important: When you delete a replicated or offline file, you delete it from both the source volume and the target. Managing Data Through the Shell Extension Tiger Bridge is integrated with Windows Explorer and displays files and folders subject to replication and space reclaiming with separate icons. 50

File icons: Managing Data Through the Shell Extension This is a replicated file (a file with copy on the target) This is a stub file (a replicated file, which has been replaced with a stub on the source volume; accessing it, will restore the replica from the target) Tiger Bridge is currently replicating, tiering or restoring the file. Wait until the operation finishes for the file icon to change. Folder icons: All files in the folder are replicated on the target. Note: This folder icon is not available, when Tiger Bridge operates in move mode. The folder contains only stub files. Important: When Tiger Bridge operates in move mode, this folder icon designates that the folder contains at least one stub file. 51

Manually Manage Data Tiger Bridge is currently replicating, tiering or restoring the files in this folder. Wait until the operation finishes for the folder icon to change. Tiger Bridge is currently scanning the contents of the folder and is unable to display its status. To manage data through the Tiger Bridge shell extension: Note: The respective commands are available only to files/folders to which they apply i.e. you cannot issue the Make offline command to a stub file, for example. 1. In Windows Explorer, right-click the file/folder you want to manage. 2. In the context menu do one of the following: Select "Tiger Bridge Replicate" to replicate the selected file or all files in the selected folder on the target. Select "Tiger Bridge Make offline" to replace the selected replicated file or all replicated files in the selected folder with stub file(s), pointing to the actual replicas on the target. Select "Tiger Bridge Restore" to restore the selected stub file or all stub files in the selected folder from the target. Important: Restoring a file from the target is possible only if there s enough free space on the volume. Keep in mind that when Tiger Bridge operates in move mode, restoring a stub file automatically deletes the replica from the target. Managing Data Through the Command-line Interface You can manually replicate files, create stub files and restore files from the target using the command-line interface. You can also use the command-line interface to synchronize the content of a source volume with its target. To manually manage data through the command-line interface: In command prompt, do one of the following: 52