User Guide Getting Started Help Center Documentation Community Training
Looker
  
English
Français
Deutsch
日本語
Restoring Backups

If you’d like to learn about creating Looker backups, checkout our Creating Backups page.

To restore Looker to a new host complete only these steps of the the Looker installation instructions:

Once the new host is prepared:

Clustered Environments

To restore the MySQL database for a clustered environment:

See the MySQL documentation for more details on how to restore MySQL databases.

Restoring Amazon S3 Backups

Looker encrypts backups before uploading them to S3. If you need to restore a backup from S3, please contact Looker support.

Restoring a Keystore-Independent Backup

Customer-hosted installations that have migrated to AES-256 GCM encryption and generated a keystore-independent backup need to update Looker’s internal database after performing a restore.

After restoring a keystore-independent backup, follow this procedure to decrypt the KEK, recrypt it using the new local keystore, and update the key entry in the internal database:

  1. Stop Looker:

    cd looker
    ./looker stop
    

    If Looker is clustered, make sure to stop every node before proceeding.

    If any nodes are still running when you later issue the restore_dr_backup command, the command will fail with the message, “There are other live nodes connected to this backend Looker database. If Looker was shutdown within the last minute, try again shortly, otherwise verify all nodes in the cluster are shut down.”

  2. Ensure the environment variable LKR_MASTER_KEY_FILE is set to the path of the CMK file used for the local keystore of the location where you restored Looker:

    export LKR_MASTER_KEY_FILE=path_to_CMK_file
    
  3. Update the internal database:

    ./looker restore_dr_backup <key_file_name>
    

    where is the path and filename of the plain text key file created when the keystore-independent backup was made. The key file has the following format:

    {"dbmk":"vr1LUwO3q6weY8iS3JykVljSjiD4m6eGk227Cs7Qu9Q=\n","backup_uid":"XCXvRa38mNeqT6+HRBCo2Q=="}
    

    where the value for dbmk is a Base64 encoding 256 bit encryption key and backup_uid is a unique name used when saving the key to the database.

After you have updated Looker’s internal database, you can start Looker normally. Once Looker is running, we recommend you delete the plain text key file used to create the keystore-independent backup.

Top