Filespace Data Migration

Team LucidLink
Team LucidLink
  • Updated

It is often necessary to migrate data between Filespaces, object storage providers, storage regions or when hosting multiple Filespaces for production vs. archive purposes. 

Additionally, you might also require data recovery between snapshots and the live Filespace.

In this article we will provide guidance as to achieve such scenarios and various methods dependent on your operating system environment. 

If you require assistance, please do not hesitate to reach out to support.

To achieve this you must run multiple Filespace daemons to attach individual mount-points for each daemon and Filespace instance.

Filespaces present their data as an extension of the local operating environment. This guide is designed to leverage our Filespace mount-points however applicable to any traditional data copy between to local drives or folders. At the end of the day, think of it as any other bulk file system transfer.

Our environment will assume you have a separate data volume for your cache and provides guidance on how to achieve configurations for Linux and Windows setups. 

We recommend cache is hosted on the fastest possible disk technology (NVMe/SSD preferable) and sized to act as a suitable buffer to complement your Internet uploads. See Migration Strategies article for more on this topic. 

It is important to confirm the destination has FileSystem.ForbidSpecialCharacters disabled before beginning transfer. Depending on your Filespace version, will dictate whether FileSystem.ForbidSpecialCharacters enabled by default. See Configure Filespace Settings

Linux Migration

Screen terminal multiplexer enables the running of multiple terminal processes in the background to ensure they continue running while disconnected. 

It is always best to ensure you've appropriate space and a suitable underlying storage location for your cache therefore we will guide you through setting up our daemons.

We will assume that a recommended NVMe/SSD disk is available to host your `root-path`. 

Should a suitable device not be available to the system to separate your cache/metadata from the system disk, merely remove `--root-path` option from command-line daemon instructions. 

Example environment with Filespace 1 as our source migrating to Filespace 2 for our destination, utilizing a 300GB SSD `/mnt/data` metadata and cache location root-path.

1. Prepare Linux machine or VM and configure cache/metadata root-path data location.

    a. Install Lucid

sudo apt update
sudo wget -O lucidinstaller.deb
sudo apt install ./lucidinstaller.deb -y

    b. Prepare NVMe for cache (adjust /dev/nvme1n1 accordingly lsblk output)

sudo mkfs -t ext4 /dev/nvme1n1
sudo mkdir /mnt/data
sudo mount /dev/nvme1n1 /mnt/data
sudo chmod 777 /mnt/data

    c. Add fstab entry

sudo nano /etc/fstab 
    /dev/nvme1n1       /mnt/data   ext4    defaults,nofail        0       0  

    d. Reboot for fun and test fstab

sudo reboot

    e. Ensure NVMe mounted after reboot, fstab working

ls /mnt/data -lh

2. Share read-only credentials to Filespace 1 source. either / share or required shares.

3. Enable read-write credentials to Filespace 2 destination. this could be in a share for migration purposes and the client can cut/paste the data into required locations at a later date 

Cut/paste vs. copy/paste is a metadata transaction and doesn't physically move data inside Filespace (egress out and ingest an independent copy).

4. Configure Filespace 1 instance for our source mount-point

screen -S Filespace1 -dm lucid --instance 1 daemon --fs filespace1.domain --user fsuser --password userpwd --mount-point /mnt/filespace1 --root-path /mnt/data/lucid

5. Configure Filespace 2 instance for our destination mount-point

screen -S Filespace2 -dm lucid --instance 2 daemon --fs filespace2.domain --user fsuser --password userpwd --mount-point /mnt/filespace2 --root-path /mnt/data/lucid

6. Set caches, leaving free space on /mnt/data for metadata

    a. set Filespace 1 cache 

lucid --instance 1 config --set --local --DataCache.Size 100G

    b. set Filespace 2 cache

lucid --instance 2 config --set --local --DataCache.Size 100G

7. Rsync /mnt/filespace1 to /mnt/filespace2

screen -S Rsync -dm rsync -aAXvP /mnt/filespace1 /mnt/filespace2 --log-file=/mnt/data/lucid/logfile.txt

8. Monitor Screen sessions

    a. List sessions

screen -ls

    b. Attach to session

screen -r <session>

    c. Detach from session

ctrl+a d


Windows Migration

As Windows doesn't have a terminal multiplexer like Screen it would probably be best to setup the Lucid daemons as NSSM services to run our 2x source and destination Filespace instance daemons.

We will utilize Robocopy in a Powershell prompt, outputting to our screen for progress and a log file.

We will assume in our environment example you will be assigning a specific disk for your cache and metadata to ensure suitable capacity and performance. 

If you will be leveraging defaults remove and ignore `root-path` options.

1. Provision read-only credentials to Filespace 1 source. either / share or required shares.

2. Assign read-write credentials to Filespace 2 destination. this could be in a share for migration purposes and the client can cut/paste the data into required locations at a later date 

Cut/paste not copy/paste is metadata transaction and doesn't move data inside Filespace.

3. Prepare cache/metadata data location via Disk Manager.

    a. Example environment with Filespace 1 to Filespace 2 and 300GB SSD E:\ metadata and cache location root-path.

4. Configure Filespace 1 instance.

    nssm install Filespace1 "C:\Program Files\Lucid\resources\Lucid.exe" --instance 1 daemon --fs filespace1.domain --user fsuser --password userpwd --mount-point c:\filespace1 --root-path e:\lucid

    nssm set Filespace1 start service_delayed_auto_start

    nssm start Filespace1

5. Configure Filespace 2 instance.

    nssm install Filespace2 "C:\Program Files\Lucid\resources\Lucid.exe" --instance 2 daemon --fs filespace2.domain --user fsuser --password userpwd --mount-point c:\filespace2 --root-path e:\lucid

    nssm set Filespace2 start service_delayed_auto_start

    nssm start Filespace2

6. Set caches, 2x 100GB out of 300GB leaving free space on E:\ for metadata.

    a. set Filespace 1 cache 

    lucid --instance 1 config --set --local --DataCache.Size 100G

    b. set Filespace 2 cache

    lucid --instance 2 config --set --local --DataCache.Size 100G

7. Robocopy process with log and output on screen.

    powershell -command "robocopy c:\filespace1 c:\filespace2 /e /z /mt /r:10 /w:10 /np | tee 'e:\logfile.txt'"


Efficient Snapshot Recovery

Applying a similar methodology to migrating data between a snapshot and the live Filespace. 

You can adjust accordingly the instance daemons to attach to a snapshot.

1. Retrieve your snapshot <id>.

lucid snapshot --list

2. Once you've identified your snapshot ID you can add it to your Filespace daemon instance with the following option

--snapshot <id>

3. Adjust your daemon instances for your Screen session or daemon processes and/or services.


lucid --instance 1 daemon --fs <filespace.domain> --user <fsuser> --password <userpwd> --mount-point /mnt/filespace
lucid --instance 2 daemon --fs <filespace.domain> --user <fsuser> --password <userpwd> --mount-point /mnt/snapshot --snapshot <id>


lucid --instance 1 daemon --fs <filespace.domain> --user <fsuser> --password <userpwd> --mount-point c:\filespace
lucid --instance 2 daemon --fs <filespace.domain> --user <fsuser> --password <userpwd> --mount-point c:\snapshot --snapshot <id>

4. Transfer your data dependant on your operating system and data recovery/transfer requirement preferences. 


rsync -aAXvP /mnt/snapshot /mnt/filespace --log-file=/home/<user>/logfile.txt


robocopy c:\snapshot c:\filespace /e /z /mir
Note: this Robocopy /mir example will replace/purge data in the live Filespace

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request



Article is closed for comments.