Skip to main content

Restores

Overview​

The Restore feature in Lium allows you to restore backups of your data into running pods. Learn how backups work here.

How to Restore Backups​

Option 1: Restore Backup into Running Pod​

This option allows you to select a backup from a running pod and restore it to a target pod.

  • Step 1: Navigate to the "Your Pod" page of the pod that has backup configuration and backups
  • Step 2: Click the "Backups" tab
  • Step 3: Click the "Restore" button
  • Step 4: Configure the restore modal:
    • Target Pod: The pod where the selected backup will be restored
    • Restore Path: The directory path in the target pod where the backup will be extracted. Important: The restore path must be a subdirectory of the target pod's volume path

Option 2: Configure Restore When Deploying a Pod​

This option allows you to select a backup during the pod deployment process.

  • Step 1: Go to "Browse Pods" and click the "Rent Now" button
  • Step 2: At the bottom, locate the "Restore" section
  • Step 3: Click the "Select a Backup" button
  • Step 4: Configure the restore settings in the modal:
    • Select from currently running pods. Once a pod is selected, its available backups will be displayed. Choose the backup you want to restore
    • Restore Path: The directory in the deploying pod where the backup will be extracted. This must be a subdirectory of the volume of the selected template

Restore Path​

  • What it is: The directory path where the backup ZIP file will be extracted
Requirements

Must be a subdirectory of the pod's local volume mount path (default local volume path is /root). Do not use external volumes that mount inside /mnt.

Valid Examples ✅

/root                       # ✅ Valid: entire volume mount (restores everything)
/root/models                # ✅ Valid: subdirectory of /root volume mount
/root/checkpoints          # ✅ Valid: subdirectory of /root volume mount  
/root/project/data         # ✅ Valid: nested subdirectory of /root volume mount

Invalid Examples ❌

/home/user/documents       # ❌ Invalid: not under /root volume mount path
/tmp/backup                # ❌ Invalid: temporary directory, not persistent storage
/var/log                   # ❌ Invalid: system directory outside volume mount

Why the distinction matters:

  • Valid paths are subdirectories within your local volume mount (/root), ensuring data persists and is accessible for restore operations
  • Invalid paths point to non-persistent storage or system directories, which can cause restore failures

View Restore History​

  • Navigate to the "Your Pod" page
  • Click the "Restores" tab