--- title: "Moving a Metadata Database" slug: "moving-a-metadata-database" updated: 2024-03-24T15:59:36Z published: 2024-03-24T15:59:36Z canonical: "skthelp.syniti.com/moving-a-metadata-database" --- > ## Documentation Index > Fetch the complete documentation index at: https://skthelp.syniti.com/llms.txt > Use this file to discover all available pages before exploring further. # Moving a Metadata Database If you need to move your Metadata database to a different server, you can create a backup of the current metadata using the tools available in the Management Center. The metadata (without the current connection details) is saved to an XML file. You can then create a new metadata connection and use the backup file to create the metadata using the new connection. To save your existing Metadata database as a backup: 1. Shut down the Replication Agent. 2. In the Management Center, select the metadata for which you want to create a backup. 3. From the main menu bar, choose **Metadata**, then **Backup Metadata...**. 4. In the Save Metadata Backup dialog, choose a folder and type a file name. 5. Click **Save** to save the metadata in an XML file. To use the Metadata backup file for a new database server: 1. In the Management Center, from the main menu bar, choose **Metadata**, then **Add New Metadata...**. 2. In the Metadata Connection wizard **Select Provider** screen, type a name for the new metadata. This name does not have to match the name of the metadata that you are moving. 3. Specify the .NET provider that you plan to use for the new database server. 4. In the **Set Connection String** screen, provide the connection information for the new database server. 5. In the **Define Metadata** screen, select the option **Create a new metadata database**. 6. Check the option **Restore the metadata set from a backup file**. 7. Enter the pathname to the file you saved in step 4 above. 8. Click **Next**, then **Finish** to complete the wizard. 9. Clear out the DBMoto.log file. 10. Start the Replication Agent and monitor the DBMoto.log file for errors.