This article applies to these versions of LandingLens:
            LandingLens            LandingLens on Snowflake
In v1_2.45 and later, you can back up and restore the LandingLens application. Having backup versions of the LandingLens application can be helpful if data is deleted that needs to be later recovered. For example, if a project in LandingLens is accidentally deleted, you can restore an earlier version of LandingLens that has that project. If the LandingLens application is deleted, restoring a backup file is the only way to recover it.

​
Process Overview

In Snowsight, you configure how often you want a backup to be saved and the maximum number of backups that should be created. LandingLens then automatically creates backup files based on that schedule. After the maximum number of backup files are created, LandingLens will delete the oldest file when it creates a new file. You can restore a backup by running SQL commands in Snowsight.

​
Backup Best Practices

​
Should I create backups?

The ability to back up LandingLens allows organizations to comply with their disaster recovery policies. The need for a backup depends on your organization’s use of LandingLens and how much downtime and data loss is acceptable in the event of a disaster. If LandingLens backups are not created, Snowflake support may be able to assist with data loss in some situations, but the turnaround time may be longer.

​
How often should I create backups?

The backup frequency depends on your organization’s disaster recovery, compliance, and operational needs. As a guideline, we recommend backing up LandingLens at least once a day.

​
Data in Backup Files

The backup files contain:
  • Images uploaded to projects
  • Models created in projects
  • The labeling, training and inference work

​
How Does Suspending the LandingLens App Impact Backups?

Backup files are not created when the LandingLens application is suspended. Backup files will continue to be created once the LandingLens app resumes. For more information about suspending and resuming the app, go to Snowflake Credit Management.

​
Create Backups of LandingLens

You can configure backup files of LandingLens to be automatically saved to a Snowflake stage.
  1. Create or identify the Snowflake stage that will store the backup files.
  2. Grant LandingLens access to the stage that will store the backups. To do this, go to Grant LandingLens Access to Stages. (You can also find the SQL commands in the app in Snowsight here: Settings > Backup Configuration.)
  3. Open Snowsight.
  4. Go to Data Products > Apps > LandingLens Visual AI Platform.
  5. Click Launch App.
  6. Click Settings.
  7. Expand the LandingLens Configs section.
  8. Enter the location of the stage in the Backup to stage field, using this format: db_name.schema_name.stage_name.
  9. Specify how often you want a backup to be saved by entering a number in the Every box and selecting either Hours or Days from the drop-down menu.
  10. Enter the maximum number of backups to save in the Max backups to keep field.
  11. Click Save. backupToStage_1
  12. Click Main.
  13. Click Refresh Installation. The installation must be refreshed for the changes to go into effect. LLSF_refreshInstall_staging

​
Get Backup Timestamps and Access Backup Files

If you want to restore a backup of LandingLens, you will run a SQL command that includes the filename of the backup file. Backup files use the following naming convention, where <TIMESTAMP> is the date and time the file was created: landinglens-backup-<TIMESTAMP>. The timestamp uses the ISO 8601 format: YYYYMMDDTHHMMSS. For example, the timestamp 20250128T135104 indicates that the backup file was created on January 28, 2025, at 13:51:04. To view the backup files so that you can get the timestamp, run the following command: 
LIST @<YOUR_DB>.<YOUR_SCHEMA>.<YOUR_STAGE> PATTERN='landinglens-backup-*';
Or, you can open Snowsight and navigate to the stage that you’ve selected to save backup files to. backups_stage

​
Restoring Backups of LandingLens

Before restoring a backup, read this entire section to understand the temporary app downtime and potential for data loss.

​
Restoring a Backup Replaces All Current Data

If you restore a backup, any data created in LandingLens after the backup was created will be lost. This includes but is not limited to new projects, uploaded images, and deployments. For example, if you create a project on Tuesday and then restore a backup from Monday, the new project will be lost.

​
Restoring a Backup Doesn’t Change the App Version

Restoring a backup doesn’t change the LandingLens app version. For example, if you are using LandingLens v1_2.47 and restore a backup created in v1_2.45, your app will remain on v1_2.47.

​
Restore a Backup

The process to restore a backup takes about 15 to 20 minutes. During that time, users will not be able to access LandingLens.
  1. If the LandingLens application has been deleted, re-install it and grant it access to the stage that has the backup files.
  2. Ensure that the LandingLens application is running (in other words, that it is not suspended). To do this:
    1. Open Snowsight.
    2. Go to Data Products > Apps > LandingLens Visual AI Platform.
    3. Click Launch App.
    4. Check that each service Status is Ready, Done, or Present. If any of the services aren’t running, resume the app. LLSF_services_ready
  3. From the APP_WIZARD page, click Support.
  4. Select the checkbox to acknowledge that running commands here may perform actions that can’t be undone.
  5. Expand the SQL Passthrough section.
  6. Enter the following command in the SQL Statement field. Replace these placeholders with your information: <YOUR_DB>, <YOUR_SCHEMA>, <YOUR_STAGE>, and <TIMESTAMP>. To get the <TIMESTAMP>, go to Get Backup Timestamps and Access Backup Files. 
    CALL core.restore_backup('@<YOUR_DB>.<YOUR_SCHEMA>.<YOUR_STAGE>/landinglens-backup-<TIMESTAMP>');
  7. Click Run. restore_backup_SQL_passthrough
  8. Once the process is complete, the following message displays. 
    **Restore from backup @<YOUR_DB>.<YOUR_SCHEMA>.<YOUR_STAGE>/landinglens-backup-<TIMESTAMP> complete!

​
Check the Status of the Restore Process

If you’ve started the process to restore a backup file, you can check the status by running this command: 
CALL core.check_logs('backupmanager.restore_backup', 
'0', 'backupmanager-app-lndsvc');

​
Application Backups (If No Backup Location Is Set)

If a backup stage is not configured, LandingLens on Snowflake has a mechanism to create application backup files. These can be used to help restore the LandingLens application, even if your organization hasn’t manually set up backup files.

​
What Do the Application Backup Files Contain?

The application backup files contain data about the LandingLens application itself, which makes it easier to re-install the application if it is deleted. The application backup files do NOT contain images, models, or labeling, training, and inference work.

​
When Are the Application Backup Files Created?

The application backup files are created in the following scenarios:
  • You have not set up the backup settings. In this case, application backup files will be saved every 1 hour and 4 backups will be retained.
  • You set up the backup recurrence and max number of backups but left the Backup to stage field blank. In this case, backup files are saved based on the schedule you set.

​
Where Are the Application Backup Files Saved?

The application backup files are saved to this internal stage: core.backups.

​
Manage and Restore the Application Backup Files

To check the list of application backup files and their timestamps in the default location, run the following command in the Get Backup Timestamps and Access Backup Files procedure. 
LIST @core.backups PATTERN = 'landinglens-backup-.*manifest.json';
To restore the application backup files from the default location, run the following command in the Restore a Backup procedure. Replace <TIMESTAMP> with the timestamp for the backup file you want to restore. 
CALL core.restore_backup('@core.backups/landinglens-backup-<TIMESTAMP>')