Here is a quick checklist for Best Practices to be followed when deploying Project Turbo. For details scroll down past the Summary
1. Is Project Turbo the right Hybrid Solution for your deployment? Take a quick survey to find out - link
2. Review the Product Guide - Link
3. Right size the Data Disk based on the folders being synchronized
4. Provisioning the Data disk and increase the size before initial boot
5. Scheduling an Install during Off-Peak hours
6. Deploying the device close to Users
7. Assign a Static IP or Dynamic IP with reservation to the device
8. Selecting Folders that are actively used by users in a certain location to Synchronize
9. Complete initial full sync before rolling out to users
10. Limit Groups added to device based on users in a given location
11. Follow best practices on rolling out Egnyte Connect Desktop App
12. Scheduling synced folder changes during off peak hours
13. Consider a second ISP connection in case of primary WAN failure
1. Is Project Turbo the right Hybrid Solution for your deployment?
Project Turbo is a new product that still does not support all the use cases that are supported on Storage Sync. It is recommended that IT administrators take the checklist questionnaire to ensure that the hybrid solution will meet their requirements. Click on the link to complete the checklist.
2. Review the Product Guide
It is recommended that IT administrators review the Product Guide before installation. Click on the link for the Product Guide.
3. Right size the Data Disk
IT administrators are recommended to review the size of folders they are synchronizing and also consider the rate at which the data usage is growing in the specific folders before provisioning the data disk. Provisioning a smaller size of data disk can lead to sync failures and errors.
4. Provisioning the Data disk (Initial install & Increasing size)
The installer creates two disks, system disk and data disk. The data disk is sized at 50 GB by default. IT administrators are required to increase the size of the data disk before they initially boot the VM up for the first time. Any effort to re-size/delete-add the data disk after initial install can lead to disk corruption.Refer to the Increasing Storage and adding new disks section of the Product Guide for details.
Note: Thin and Thick provisioning of disks are supported, recommendation is to use fixed limits if the disk is provisioned as a Thin disk.
5. Scheduling an Install during Off-Peak hours
The sync engine follows a sophisticated algorithm to scan the folder structure and to synchronize folder and files locally. Depending on the size of folders that are being synchronized this operation could take anywhere from a few mins to days. It is recommended that IT administrators set up the device during off peak hours and allow the first full sync operation to complete over the weekend.
6. Deploying close to Users
Project Turbo provides maximum performance benefit when deployed close to the users. It is recommended that administrators identify the location that provides the least latency between users and the device before the install. For example deploying in a remote construction site where designers and construction engineers are actively accessing content is more efficient that deploying the Project Turbo in a data center in the same scenario.
7. IP Addressing
The discovery process of the Egnyte Connect Desktop App utilizes the FQDN and IP address it gets from the CFS and perform a latency test to identify the best device to connect. It is recommended that the Project Turbo is given a static IP address and if this is not feasible for your deployment, it is recommended that a DHCP address with reservation is provided to ensure the device received the same IP address at every boot. Refer to the Configuring Static IP section of the Product Guide for details.
8. Selecting Folders to Synchronize
Synchronizing folders to Project Turbo consumes bandwidth and disk space. In order to be efficient, It is recommended that IT administrators only sync select folders that are useful and the ones that will provide the most benefit when available at LAN speeds to users. For Example, Instead of synchronizing the entire /Shared or /Private Folders consider synchronizing selected sub-folders /Shared/Marketing and selected private folders of users in the remote location like /Private/ACME.
9. Complete initial sync before rolling out to users
Depending on the size of folders that are being synchronized this operation could take anywhere from a few mins to days. It is recommended that IT administrators wait for the first full sync to be successfully complete before rolling the device out to user groups. Onboarding users and having them connect to project Turbo when the initial sync is in progress can cause file conflicts and duplication.
10. Limiting Groups added to the device
Egnyte Connect Desktop App is architected to proxy all user requests through Project Turbo if the user belongs to the group that is added to the device and if the user is Turbo connected. IT admins are recommended to only add groups of users that are resident in a particular location where the device is deployed.
For example, Consider 2 remote offices (NY and SFO) with Project Turbo
NY Office: /Shared/Sales and users are from the sales group
SFO Office: /Shared/Marketing and users are from the marketing group
It is recommended that the NY Project Turbo only syncs /Shared/Sales and adds users in the sales group while the SFO Project Turbo only syncs /Shared/Marketing and adds users in the marketing group
11. Rolling out Egnyte Connect Desktop App
12. Changing folder selection to be synced
It is recommended that IT administrators schedule changes to the folders synced to the device during off peak hours to allow enough time for rescan sync to be completed
13. Backup WAN link
It is recommended that you consider a backup WAN link as Turbo requires a persistent connection with cloud to check for locks and does not support offline mode