If you've [chosen to manage your own Looker instance](https://docs.cloud.google.com/looker/docs/2622/choosing-hosting-option.md.txt), this page provides information about ongoing maintenance. If you're looking for initial installation steps, refer to the [Customer-hosted installation steps](https://docs.cloud.google.com/looker/docs/2622/customer-hosted-installation-steps.md.txt) documentation.

Select from the following topics to learn more about hosting a Looker instance:

- [Updating a customer-hosted Looker instance](https://docs.cloud.google.com/looker/docs/2622/updating-looker-instance): Update Looker to stay current with new features and fixes.
- [Auto-provisioning a new Looker instance](https://docs.cloud.google.com/looker/docs/2622/auto-provisioning-new-looker-instance.md.txt): Automatically provision a new instance with a license key, a URL, and an initial user.
- [Moving Looker to a new host](https://docs.cloud.google.com/looker/docs/2622/moving-to-new-host): Move Looker from one host to another.
- [Clustering Looker](https://docs.cloud.google.com/looker/docs/2622/clustering-looker.md.txt): Create a clustered Looker configuration.
- [Configuration management tools](https://docs.cloud.google.com/looker/docs/2622/configuration-management-tools.md.txt): View an example Ansible role for a simplified Looker deployment.
- [Recommended Java memory settings](https://docs.cloud.google.com/looker/docs/2622/recommended-java-memory-settings): Allocate the appropriate amount of memory to the Looker application.
- [Archiving Looker log files](https://docs.cloud.google.com/looker/docs/2622/archiving-log-files.md.txt): Manage Looker log files to preserve disk space.
- [Restoring backups](https://docs.cloud.google.com/looker/docs/2622/restoring-backups): Restore Looker to a new host or to a cluster.
- [Migrating the Looker backend database to MySQL](https://docs.cloud.google.com/looker/docs/2622/migrating-looker-backend-db-to-mysql.md.txt): For larger instances, migrate from the Looker HyperSQL internal database to a MySQL backend database.
- [Migrating to AES-256 GCM encryption](https://docs.cloud.google.com/looker/docs/2622/migrating-to-aes-256-gcm-encryption.md.txt): Migrate an existing Looker instance to AES-256 GCM encryption for internal data encryption.
- [Changing Looker encryption keys](https://docs.cloud.google.com/looker/docs/2622/changing-encryption-keys.md.txt): Change the encryption key that Looker uses to encrypt internal data.
- [Enabling a Redis cache on a customer-hosted instance](https://docs.cloud.google.com/looker/docs/2622/enabling-redis-cache-on-customer-hosted-instance.md.txt): Enable a Redis cache on a customer-hosted instance for improved cache performance.
- [Upgrading to OpenJDK 11](https://docs.cloud.google.com/looker/docs/2622/upgrading-to-openjdk-11-customer-hosted-instance): Upgrade from OpenJDK version 8 to version 11.
- [Upgrading to OpenJDK 21](https://docs.cloud.google.com/looker/docs/2622/upgrading-to-openjdk-21-customer-hosted-instance): Upgrade from OpenJDK version 11 to version 21.
- [Enabling FIPS 140-2 level 1 compliance](https://docs.cloud.google.com/looker/docs/2622/fips-mode.md.txt): Enable FIPS 140-2 level 1 encryption on a new customer-hosted Looker instance.