Importing Repositories into VisualSVN Server

This article helps you to import an existing repository from another VisualSVN Server installation or from another Subversion server or hosting.

Select an import method

VisualSVN Server provides two different import methods:

  • Copy repository from another location. Select this method to import an existing repository from another location by making its hot copy. А hot copy is a full repository snapshot that includes all versioned changes, hook scripts, configured permissions and other repository settings. This is a preferred way of importing repositories, unless your data is stored in the form of a dump file or you are importing an incompatible repository.
  • Load repository from a dump file. Select this method to create a new repository and load data to it from a dump file. Dump files contain only versioned changes in a portable format, so you may need to reconfigure repository hooks and permissions after the import.
Note
To restore a repository from a backup file (*.vsvnbak), please use the dedicated Restore Repository wizard. For additional details, see the KB106: Getting started with Backup and Restore article.

Copy repository from another location

This method allows you to import any repository that uses the FSFS or VDFS backend data store type. When using this method, VisualSVN Server performs a hot copy of a source repository. An imported repository will include all versioned changes, hook scripts, configured permissions and other repository settings.

Before you begin the import process, consider the following prerequisites:

  • Source repository services are stopped. Although the copy operation can be safely performed for a repository that is currently in use, it is strongly recommended to stop the source repository services in order to prevent new changes in the source repository. Otherwise, if such changes occur in the middle of the import process, the imported version of the repository may not include them.
  • Source repository is accessible. You should be able to access your source repository from the computer where it is being imported to. If the source repository is stored on a network share, please see the Importing repositories from a network share section for additional instructions.

Once the prerequisites are met, perform the following steps to copy a repository from another location:

  1. Start the VisualSVN Server Manager console.
  2. Right-click the Repositories node and select Import Existing Repository.
  3. Select Copy repository from another location and click Next.
  4. Specify the source repository location and click Next.
  5. Specify the destination repository name and click Import.
  6. Click Finish after the import has successfully completed.

The specified repository will be copied into the repositories root directory and will be available under the Repositories node in VisualSVN Server Manager.

Tip
Alternatively, a repository can be imported using a PowerShell cmdlet. Learn more about the Import-SvnRepository cmdlet in the dedicated section of the KB88: VisualSVN Server PowerShell Cmdlet Reference article.

Load repository from a dump file

This method allows you to import a repository of any given format by loading it from a repository dump file. The repository dump file format is independent of the repository backend data store type or its version. For example, it can be used to migrate a BDB-backed repository to the FSFS backend.

Tip
VisualSVN Server supports loading GZIP-compressed dump files (*.gz). Therefore, you do not need to unpack compressed dump files and can load them as is.

Note that a repository dump file does not carry any information about the hook scripts, configured permissions and other repository settings, so you may need to configure them after the import.

Before you begin the import process, consider the following prerequisites:

  • Source repository is exported to a repository dump file. To use this method, you need to first generate a dump file for your source repository. See the KB173: Generating a repository dump file article for instructions.
  • Repository dump file is accessible. You should be able to access your dump file from the computer where it is being imported to. If the repository dump file is stored on a network share, please see the Importing repositories from a network share section for additional instructions.

Once the prerequisites are met, perform the following steps to load a repository from a dump file:

  1. Start the VisualSVN Server Manager console.
  2. Right-click the Repositories node and select Import Existing Repository.
  3. Select Load repository from a dump file and click Next.
  4. Specify the dump file location and click Next.
  5. Specify the destination repository name and click Next.
  6. Specify initial access permissions for the destination repository and click Import.
  7. Click Finish after the import has successfully completed.

The destination repository will be created using the data in the selected dump file and will become available under the Repositories node in VisualSVN Server Manager.

Tip
Alternatively, a repository dump can be imported using a PowerShell cmdlet. Learn more about the Import-SvnRepository cmdlet in the dedicated section of the KB88: VisualSVN Server PowerShell Cmdlet Reference article.

Importing repositories from a network share

You should be able to access your import source from the computer where it is being imported to. If you are importing from a network share, make sure that:

  • Share and NTFS access permissions to your import source are properly configured for the account of the VisualSVN Server administrator who is performing the import operation.
  • A UNC path is used rather than a mapped network drive. Mapped network drives are mapped on a per-user basis and may be inaccessible in the context of the import operation.

See also

KB80: Repository types available in VisualSVN Server
KB135: Understanding the Subversion repository types and formats
KB142: Upgrading the filesystem format of a repository

Last Modified: