If you've chosen to manage your own Looker instance, this page provides information about ongoing maintenance. If you're looking for initial installation steps, refer to the Customer-hosted installation steps documentation.
Select from the following topics to learn more about hosting a Looker instance:
- Updating a customer-hosted Looker instance: Update Looker to stay current with new features and fixes.
- Auto-provisioning a new Looker instance: Automatically provision a new instance with a license key, a URL, and an initial user.
- Moving Looker to a new host: Move Looker from one host to another.
- Clustering Looker: Create a clustered Looker configuration.
- Configuration management tools: View an example Ansible role for a simplified Looker deployment.
- Recommended Java memory settings: Allocate the appropriate amount of memory to the Looker application.
- Archiving Looker log files: Manage Looker log files to preserve disk space.
- Restoring backups: Restore Looker to a new host or to a cluster.
- Migrating the Looker backend database to MySQL: For larger instances, migrate from the Looker HyperSQL internal database to a MySQL backend database.
- Migrating to AES-256 GCM encryption: Migrate an existing Looker instance to AES-256 GCM encryption for internal data encryption.
- Changing Looker encryption keys: Change the encryption key that Looker uses to encrypt internal data.
- Enabling a Redis cache on a customer-hosted instance: Enable a Redis cache on a customer-hosted instance for improved cache performance.
- Upgrading to OpenJDK 11: Upgrade from OpenJDK version 8 to version 11.