🐧
Linux Control Center
EN
EN
  • Introduction - User Manual
  • Requirements
    • Server Requirements
    • Client Requirements
  • Quick Start
  • Setup and Installation
  • Dashboard
  • Discover
    • Linux Control Center Discover
    • BeyondTrust Password Safe
  • Host Actions
    • Get Info
    • Package Check Update
    • Package Update
    • Package Vulnerable Update
    • Package Hold
    • Package Install
    • Package Remove
    • Account Add
    • Account Del
    • Account Expire
    • Account Lock
    • Account UnLock
    • File Add
    • File Del
    • File Download
    • Manage Host Service
    • Host Ping
    • Host Reboot
    • Host Shutdown
    • Insert Group
    • Check Vulnerability
    • Execute Custom Playbook
    • Execute Custom Scripts
    • Tenable Launch Scan
    • Tenable Sync Results
    • Delete Hosts
  • Host Groups
  • Managed Account
    • Create Managed Account
  • Managed Files
    • Create Managed File
  • 7 Library
    • Install Tenable Agent
  • 7 VulnDB-API
  • Custom Scripts
    • Linux Scripts
    • BeyondTrust Password Safe Secrets
  • Custom Playbooks
  • Hook Bridge
    • Hook Bridge
  • Workflow
    • Create Workflow
  • Assisted Workflow
  • Scheduler
  • Unmanaged Hosts
    • Microsoft Windows
  • Settings and Integrations
    • Settings
      • License
      • Worker
      • Nodes
      • Certificate
      • LCC Management
      • Diagnostic
      • Linux Credentials
      • Regions
      • Syncronized Files
      • Notifications
        • SMTP
        • Teams
        • Telegram
      • Parameters
      • Discover Timeout
      • Backup and Restore
    • Integrations
      • BeyondTrust
        • Password Safe
        • Privileged Remote Access
      • VMWare
      • Nutanix
      • Tenable
        • Security Center
        • Cloud Security
    • User Management
      • Console Users
        • Create Super User
        • Create Group Users
      • TOTP
      • Providers
        • SAML
          • Cisco Duo
          • Entra ID
      • Authentication
  • Release Notes
Powered by GitBook
On this page
  • Version
  • Requirements
  • Overview
  • Objective
  • Default Backup Directory
  • Stopping Containers
  • Backup Configuration Files
  • Database Backup
  • Restoring Backup
  • Starting the Containers
  1. Settings and Integrations
  2. Settings

Backup and Restore

Version

  • Linux Control Center = 2.10.X or higher

Requirements

  • SSH access to the LCC Host with root user

Overview

  • This guide provides information and step-by-step instructions for backing up and restoring the LCC

Objective

  • Demonstrate the complete backup and restore process of the LCC through the CLI interface.

Default Backup Directory

We strongly recommend that the generated backups be copied to a safe location, ensuring data preservation in case any intervention is necessary in the future.

Backup destination directory: /opt/lcc/bkp/

The configuration backup files will have a name in the format backup_config_YYYY-MM-DD_HH-MM-SS.tar.gz, indicating the year, month, day, hour, minute and seconds in which the backup was created. These files contain the settings required for LCC to work.

The database backup file will be named in the format lcc_db_YYYY-MM-DD_HH-MM-SS.sql, following the same pattern. This file stores the entire database, allowing complete recovery of the stored information.

Stopping Containers

  1. Before performing the backup, it is necessary to stop the LCC Container processes separately for greater data integrity.

  2. Container lcc_console Command: docker stop lcc_console

  3. Container lcc_worker Command: docker stop lcc_worker

  4. Container lcc_alert_report Command: docker stop lcc_alert_report

  5. See the example in the image below:

Backup Configuration Files

  1. This command backs up all files with the .yml extension that were generated during installation. These files are essential for LCC to work.

Command: lcc-cli backup -a

  1. The backup will be compressed in the tar.gz extension

The LCC database is encrypted, and within this compressed backup there will be a file called crypt.yml, which is the key to decrypt during the restore.

Without this key, it will be impossible to restore the database.

Database Backup

  1. To back up the LCC database, run the command below;

Command: lcc-cli database --backup

  1. The backup will have the .sql extension with the date and time the backup creation command was executed.

Restoring Backup

Command: tar -xzvf file_name.tar.gz -C /

![](/pt-br/images/backup_and_restore/extracting_config.png)

Command: lcc-cli database --restore file_name.sql

  1. Check if you are using the correct backup and confirm by typing y and pressing enter

Starting the Containers

  1. After the restoration is complete, run the commands to start the Containers.

  2. Container lcc_console Command: docker start lcc_console

  3. Container lcc_worker Command: docker start lcc_worker

  4. Container lcc_alert_report Command: docker start lcc_alert_report

  5. See the example in the image below:

  6. The LCC will be ready for use normally after the Containers are initialized.

PreviousDiscover TimeoutNextIntegrations

Last updated 11 days ago

To restore the LCC, you must extract all to the system root directory / with the root user

After extracting the files, run the command to restore the LCC from the .sql file created in the step.

Configuration Files
Database Backup