WYNTK: LucidLink

Support

https://support.lucidlink.com/

Contact Rich Werhun - Sales Engineer 570-417-2169 or 570-991-5157

rich.werhun@lucidlink.com

Separate file spaces for data and backups (recommended)

Built-in/subscribe within LucidLink dashboard

• IBM (Files) - Advanced
• Wasabi (Backups) - Basic

NOTE: For fast connection, can use file space with 1 MB (as opposed to 256kb chunks - only for good internet connections

Manage Filespace Users (Must be done using Desktop client)

https://support.lucidlink.com/support/solutions/articles/31000148502-manage-filespace-users-

Create a Snapshot Schedule for your Filespace (GUI)

**Lucidlink will now be billing for snapshots as of 2022-09 **

Backup Filespaces use the following snapshots (Keep total under 300):

• Hourly - 168 (7 days)
• Daily - 30-90 (30-90 days)

This will avoid excessive billing for more than 1 month due to deleted backup chains (snapshots)

NOTE: Deleting snapshot schedule does NOT destroy snapshots. It creates snapshots and schedule garbage collector

• On new setups, delete default schedule, and create one from above
• If created later (i.e. after initial snapshit schedule runs), manually delete snapshots older than longest retention period (i.e. 30 days) to avoid excess billing/lingering snapshots
• Preserve snapshots (i.e. cybersecurity), just delete the schedule. Snapshots will remain as long as filespace is pad for

File server replacements use the following snapshots:

• 15 minutes - Retention of 16 (4 hours). 
• Hourly - 168 (7 days)
• Daily - 36 (1 month)
• Weekly - 28 (6 months)
• Monthly - 13 (1 year)
• Yearly - 1+ (Based on company policy)

Lucidlink supports a maximum of 300 snapshots allowed for a Filespace. (Above is 261 + yearly)

Create a Snapshot Schedule for your Filespace (Command Prompt)

https://support.lucidlink.com/support/solutions/articles/31000150381-create-a-snapshot-schedule-for-your-filespace

Locking Filesystem extensions (Command Prompt) - May no longer need - Specifically QuickBooks

We do have a support for "on open" locking on Windows. While this is a generic functionality, it's behavior might vary depending on the particular implementation of the application (e.g. QuickBooks). From the command prompt you could try to enable a file extension that Lucid will consider for locking:

lucid config --explain --FileSystem.LockingExtensions<br> <br> Key: FileSystem.LockingExtensions<br> Description: Windows only. File extensions for which locking will be applied on open. Empty string disables file locking.<br> Value constraints: Windows only. List of comma separated strings e.g. ("docx,pptx,rvt"). Empty string disables file locking.<br> Default value: rvt,dwl,dwl2,dwt,dwg,pptx,xlsx,doc,docx

You can see which file extensions are considered by default for locking including some of the more popular applications (e.g. Word, Excel).

For example if you'd like to add .qbw extension you could run the following command from the command prompt while logged in the filespace as a root user:

lucid config --set --global --FileSystem.LockingExtensions "doc,docx,dwl,dwl2,dwt,dwg,ppt,pptx,qbb,qbw,rvt,txt,xls,xlsx"

Note that I've added the --global flag to the --set command so that any PC logged in to this filespace will read and apply this configuration. For using the --global flag you'll need to be logged in as a root user to the filespace.

• Adjust local cache to accommodate largest spf/cm file - Mind size of 'C' drive - Will need to clear in between SPFs and periodically - Adjust accordingly
• Monitor upload with desktop client (Resource monitor)
• Set ImageManager to use mapped drive ('L')
• Adjust Upload (and Download) rate so it doesn't monopolize bandwidth - Run speed test, cut in half, divide by 8
• Adjust 'Maximum upload/download connections' - especially if limited bandwidth - to avoid overrunning buffer (higher number for 4k; lower number for large files, limited bandwidth)

Overview

1. DataCache.Size = largest spf/cm file - ensure enough free space
2. FileSystem.MountPointWindows - or - FileSystem.DefaultMountPointScheme
3. ObjectScheduler.MaxDownloadRate = Leave enough headroom for remote access, cameras, etc. - MB to Mb (8:1)
4. ObjectScheudle.MaxUploadRate = same as above  

Current settings

• lucid config --list (shows you what you changed)
• lucid config --explain (Lists of available commands)

Data Cache Size (Max 1 TB)

lucid config --set --DataCache.Size 100G 

lucid deactivate 

lucid activate
	

• lucid unmount
• lucid mount l:

Start LucidLink as a Windows service (multiple FileSpace instances)

Non-Sucking Service Manager (NSSM) with LucidLink  

https://support.lucidlink.com/support/solutions/articles/31000149433-non-sucking-service-manager-nssm-with-lucidlink

To install

1. Install NSSM - https://nssm.cc/download - Move nssm.exe to c:\apps
2. Open Command Prompt as Admin - Navigate to c:\apps (or commands won't work)
3. nssm install "Lucid (filespace.demo)" "C:\Program Files\Lucid\resources\Lucid.exe" --instance 1 daemon --fs filespace.demo --user root --password 12345 --mount-point L:
4. nssm start <servicename>

NOTE: Each instance uses a different port (first instance is 0)

To edit:

1. nssm edit "<servicename>"  - Opens a GUI to edit

To remove:

1. nssm stop "<servicename>"
2. nssm remove

NOTE:

May need to stagger the start of multiple filespaces (delayed start within services) - Had pulsing 20 Mb sends