The Admin tab’s Backup panel lets you configure the backup of information stored in Looker’s
i__looker internal database.
Backups configured in the Backup panel work for instances using the internal HyperSQL database. However, especially if you use a MySQL backend database, we highly recommend that you back up your Looker instance daily using the instructions on the Creating Backups documentation page.
A backup is automatically made once per day and includes all information stored in Looker’s
i__looker internal database. This includes information about all Looks, dashboards, users, roles, and Spaces on your instance, as well as 90 days’ history of all queries performed.
There are also several other types of backups for Looker:
- Your LookML files, ssh keys, and log files. If your instance is hosted by Looker, these are backed up by Looker. If you have a customer-hosted Looker deployment, see this page for instructions on backing up your Looker data.
- LookML files. Any LookML files that have been pushed to your repository are backed up there, as discussed on the Setting Up and Testing Git.
On the Admin tab’s Backup panel, you can choose one of the following options:
Looker S3 bucket: Backups are stored in Looker’s S3 bucket.
Custom S3 bucket: Backups are stored in an S3 bucket that you specify. When you select this option, you must provide:
- The S3 Bucket Name
- The S3 Bucket Region
- The bucket S3 Key
- The bucket S3 Secret
See the Creating Backups documentation page for more information about using a custom S3 bucket for backups.
Disabled: Backups are not automatically created. We strongly recommend you do not choose this option unless you have a customer-hosted Looker deployment and have your own backup process in place. In that case, ensure that you back up your Looker instance regularly.
You will need to contact Looker support to retrieve a backup. Backups are encrypted locally before being uploaded to an S3 bucket regardless of whether you use Looker’s S3 bucket or a custom one.