Repository dump is a file that contains all repository revisions in a portable format. The repository dump file format is independent of the repository backend data store type or its version. It can be used for archiving repositories that are no longer in use, importing repositories to another location or migrating repositories to a newer backend type (e.g., migrating from BDB to FSFS).

There are several ways to export a repository dump file:

Export repository dump using VisualSVN Server Manager

VisualSVN Server 4.0 and later versions allow several export options, including exporting repositories to dump or GZIP-compressed dump.

Follow these steps to export a repository dump in VisualSVN Server:

  1. Start the VisualSVN Server Manager console.
  2. Expand the Repositories node.
  3. Right-click the repository you want to export and click All Tasks | Export Repository.
  4. Select Export repository dump and click Next.
  5. Adjust the export options if needed and click Export.
  6. Click Finish after the export is complete.

The repository dump will become available in the specified destination folder.

Export repository dump using VisualSVN Server PowerShell cmdlet

VisualSVN Server 4.0 and later versions provide the Export-SvnRepository PowerShell cmdlet to export one or multiple repositories at once. The cmdlet allows several export options, including exporting repositories to dump or GZIP-compressed dump.

For example, perform the following PowerShell command to export the contents of the MyRepo repository to a dump file:

PS C:\> Export-SvnRepository MyRepo -DestinationLocation C:\ -Format Dump

The repository dump will become available in the specified destination location.

Export repository dump using svnadmin

The svnadmin tool that comes with Subversion provides the svnadmin dump subcommand for generating a repository dump.

For example, run the following command in Windows Command Prompt (cmd.exe) or PowerShell:

svnadmin dump C:\Repositories\MyRepo --file C:\repo.dump

Note
Note It is highly recommended to use the --file option rather than the stdout redirection, because piping binary data is not supported in PowerShell and will corrupt the resulting repository dump file.

The repository dump will become available in the specified destination location.

See also

KB10: Importing Repositories into VisualSVN Server
KB80: Repository types available in VisualSVN Server

Last Modified: