--- schema_version: "1" id: f501a121914962f62ad3c4d3771b3d7ce2d3981b93a1d1476c7271de008e7a81 title: Re-Configure Tableau Server Repository collection: tableau version: next locale: en-us portal_url: https://docs.salesforce.com/tableau/next/en-us/server/server_external_repo_reconfigure.md canonical_url: https://help.tableau.com/v0.0/server/en-us/server_external_repo_reconfigure.htm source_site: help.tableau.com content_type: documentation content_hash: 9b52c3dcb9f9990efb1067a8b557fc61ed89b546d1a4ada4192f7261a4add5d1 description: Reconfigure the Tableau Server repository between local and external. --- [Skip to main content](#main-content) # Re-Configure Tableau Server Repository Your Tableau Server may be configured to use either a local or an external repository. This topic describes the steps needed to reconfigure your existing Tableau Server with one of the following options: - Move a local Tableau Server Repository to an external repository and configure your Tableau Server to use an external repository. - Move the external Tableau Server Repository to your local Tableau Server installation, and configure your Tableau Server to use the local repository. This means that the Tableau Server repository will be installed on the same machine or machines as your Tableau Server. **Note:** Tableau Server must be stopped before you can safely move the repository. To learn more about these options and external repositories, see [Tableau Server External Repository](https://help.tableau.com/v0.0/server/en-us/server_external_repo.htm). ## Move local repository to external Tableau Server must be stopped to migrate from a local repository to an external repository. Use the following steps to move Tableau Server Repository from local to external: 1. Activate the Advanced Management product key on your Tableau Server if it is not already activated. Advanced Management license is required to configure your Tableau Server with an external repository. 2. Configure Amazon PostgreSQL DB instance to use as the external repository. 1. Amazon: [Create a PostgreSQL DB Instance on AWS Relational Database Service (RDS)](https://help.tableau.com/v0.0/server/en-us/server_external_repo_configure_RDS.htm). 2. Azure Database: [Create a Azure Database PostgreSQL Instance on Azure](https://help.tableau.com/v0.0/server/en-us/server_external_repo_configure_Azure.htm). 3. Google Cloud Database: [Create a PostgreSQL Instance on Google Cloud](https://help.tableau.com/v0.0/server/en-us/server_external_repo_configure_gcp.htm) 4. Stand-alone PostgreSQL Instance: [Create a PostgreSQL Database as a Stand-alone Installation](https://help.tableau.com/v0.0/server/en-us/server_external_repo_configure_standalone.htm) . 3. Create a json file with the following configuration settings: { "flavor":"", "masterUsername":"", "masterPassword":"", "host":"", "port":5432 } - **flavor:** This is the type of external service you are going to use for Tableau Server repository. - Amazon RDS: use “rds” - Azure Database: use "azure" - Google Cloud Database: use "gcp" - Stand-alone PostgreSQL database: use "generic" - **masterUsername:** - **Amazon RDS:** Use "rails" for the user name. This is the user that you specified when creating the RDS instance. > [!IMPORTANT] > > You must use "rails" as the masterUsername. This is required for the external repository to work with Tableau Server properly. - **Azure Database, Google Cloud instance, and Stand-alone PostgreSQL instance:** Choose a user name that meets your requirements. We recommend using **postgres** as the Administrator user name. If you choose to use a different user name, make sure that the user name does not start with **pg** or **azure**. The user name also cannot be **rails**, **tblwgadmin**, **tableau**, **readonly**, or **tbladminviews**. When choosing a user name other than "postgres", after each backup restore, the suffix "\_bak" will be added to the initial "postgres" system user in the repository, such as "postgres\_bak". - **masterPassword:** This is the same password you specified when creating the PostgreSQL database instance. - **host:** This is the endpoint of your PostgreSQL database instance. - **port:** The database port you specified when creating the PostgreSQL DB instance. 4. Run the following TSM CLI command to configure Tableau Server to use external repository: `tsm topology external-services repository enable -f file.json -c .pem` **Note:** The SSL certificate is needed only if you are using encrypted connections between Tableau Server and the External Repository. If this is not a requirement for you, you must specify the `--no-ssl` option. In this case, the tsm command would look like this: `tsm topology external-services repository enable -f .json --no-ssl` The json file is the file that you created in the first step with the configuration settings. The SSL certificate file can be downloaded as described in [this topic](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/CHAP_PostgreSQL.html#PostgreSQL.Concepts.General.SSL). Running the above command will migrate the local repository to your new external PostgreSQL DB instance. ## Move external repository to local Tableau Server must be stopped to migrate from an external repository to a local repository. Use the following steps to move Tableau Server Repository from external location to the local installation: 1. Run the following TSM CLI command to move the repository to a specific node: `tsm topology external-services repository disable -n nodeN` 2. If you are setting up HA for your repository, install the repository on a second node. For more information, see [Example: Install and Configure a Three-Node HA Cluster](https://help.tableau.com/v0.0/server/en-us/distrib_ha_install_3node.htm). **Note:** To install the repository on a second node, you must run the command described in the previous step first. The first step migrates your external repository to the local repository. You can then install the repository on a second node on your Tableau Server. ## Who can do this Tableau Server Administrators can reconfigure external repository. You will also need to have access to create PostgreSQL database instance on Amazon or Azure.