The LucidLink Filespaces log-structured design and block-level data layout built on object store present a unique opportunity for granular snapshot capabilities.
Snapshots can be enabled per filespace with multiple snapshots configurable to each filespace.
Snapshots are created from the command line interface. For example: every hour, day, week, month and yearly snapshots can be created, deleted and replaced to satisfy your organization's recovery point objectives. You can automate the creation of snapshots through snapshot scheduling.
In this article, we will focus on manual snapshots and familiarize you in the process of managing your snapshots, mounting and accessing their data. Methods equally apply to snapshots created by snapshot schedules.
Accessing Your Snapshots
All snapshots can be activated via LucidLink Client dashboard or via the command line, by selecting the snapshot tab, entering your password and selecting activate snapshots. Snapshots are read-only, you can simply copy any required data out of a certain snapshot to your active Filespace.
Locate the LucidLinklogo within the Taskbar.
Once you've activated your snapshots, you will note an additional mount-point which contains all your available snapshots.
Creating and Managing Snapshots
Snapshots are managed using the LucidLink Client via the command line or terminal. You can also set a snapshot schedule, allowing you to automate snapshot creation and retention. Filespace snapshot schedules are managed centrally. Once you set up a snapshot schedule, these will be created automatically, whether the LucidLink Client is connected or not.
Each snapshot is represented by name description along with a unique identifier in order to delete your snapshot and replace it in future with an updated point in time.
usage: Lucid snapshot [options] Snapshot management. To activate a snapshot, see the options of 'lucid activate'. To schedule snapshots see 'lucid snapshot-schedule'. Options: --password password Root user's password is required for creating and deleting snapshots [--list] Display the list of existing snapshots --create [name] Create a snapshot with the specified name. Name format: a-z, A-Z, 0-9, '-_ ()'. Max length 40 chars --delete id Delete the snapshot with the specified id
lucid snapshot --create Backup Snapshot with ID 1 created.
lucid snapshot --list ID STATE NAME CREATED ON 1 valid Backup 2019-06-20 12:00
lucid snapshot --delete <id>
Activating a Snapshot via command-line interface
There are multiple ways to activate snapshots allowing read-only access.
Our CLI provides activate and daemon link modes to interface with your snapshot data. Each mode provides unique advantages depending on the use case.
To replace your existing active live Filespace mount-point with immediate access to a snapshot you can utilize activate. If you require access to snapshot data while actively connected to your Filespace you would launch a separate daemon.
You can activate an individual snapshot or all your Filespace snapshots in a single location.
Activate a snapshot:
lucid activate --snapshot <id>
Activate all snapshots:
lucid activate --all-snapshots
Note: activating your snapshot will replace your active live Filespace mount-point.
To remain linked to your live Filespace and access snapshot data use a separate LucidLink Client instance ID just like you would if you link to multiple filespace on the same system.
Launch a snapshot instance:
lucid --instance <id> daemon --fs <filespace.domain> --user <fsuser> --password <userpwd> --mount-point <mount-point> --snapshot <id>
Specify a mount-point relevant to your operating environment: Windows can be a drive letter or directory. macOS and Linux a mount-point such as within your home directory ~/snapshot
Mount all your snapshots:
lucid --instance <id> daemon --fs <filespace.domain> --user <fsuser> --password <userpwd> --mount-point <mount-point> --all-snapshots
Please reach out to LucidLink Support should you require any further assistance.
Once you've mastered manual snapshots why not implement snapshot schedules to provide far greater automated data protection:
lucid snapshot-schedule --create name --interval <m | h | d | w | mo | y>
For example, to setup grandfather-father-son (GFS) retention on your filespace, you can do the following:
lucid snapshot-schedule --create "15 minutes" --interval 15m --retention 4 --start 2000-12-31T00:00 lucid snapshot-schedule --create "Hourly" --interval 1h --retention 24 --start 2000-12-31T00:00 lucid snapshot-schedule --create "Daily" --interval 1d --retention 7 --start 2000-12-31T00:00 lucid snapshot-schedule --create "Weekly" --interval 1w --retention 4 --start 2000-12-31T00:00 lucid snapshot-schedule --create "Monthly" --interval 1mo --retention 12 --start 2000-12-31T00:00 lucid snapshot-schedule --create "Yearly" --interval 1y --retention 2 --start 2000-12-31T00:00
You do not have to specify the
--starttime, but by doing so delineates the point at which the snapshot is created. This is especially useful when you want to keep data from a specific date or time as your Daily, Weekly, Monthly or Yearly snapshot. As LucidLink calculates onward from the date specified it is possible to use a date set in the past to drive the appropriate retention behavior. The above snapshot schedule is an example, and should be modified to suit your retention needs. You will now see snapshots start showing up every 15 minute mark when you run
lucid snapshot --list.